Forum Replies Created
-
Posts
-
Hi, my apologies. Your response somehow escaped my attention.
Your archive pages do indeed have nodinex meta tags:
<meta name="robots" content="follow, noindex" />Are you using an SEO plugin like Yoast SEO or other? If so, it might be a setting in that plugin. If not, it may be coming from your theme.
If there is no option to set archive pages to “index” your best solution may be to disable the Categories and Tags sitemaps on Settings > XML Sitemap. This should not hurt your site and (according to many SEO specialists) even be better for ranking of your normal pages and posts.
Please note: I’m not an SEO specialist, but it does seem logical that excluding low value content from the index would allow more attention on high value content (read: full posts and pages). A simple first step is excluding automatic archives such as category and tag pages.
Hi Ahmed, this plugin does not set any noindex met tags or response headers. If your category and tag archive pages are showing noindex, it must be coming from somewhere else. Like a setting in an SEO plugin or your theme (like themes based on the Genesis Framework).
If you can share a link to your site, I can take a look and maybe tell you where it is coming from 🙂
Yes, meta keywords is largely ignored at this point. We kept it because it is still demanded by users…
We’re considering other features, which you can vote for here if you wish 🙂
One question: could you go to Settings > Google News > License tab, then select “Check license” and hit Save, then let me know if you get an error message that says “An error occurred, please try again.”? I wonder if there is some kind of problem reaching the update server from your site…
About the plugin updates: there is one coming soon that does include some updates to the plugin self-updater routines but I’m not aware of a fix for any admin slowdown. Nor did we get any other reports about this, so that is why I wonder if there is something else going wrong.
Still, I can send you the development version if you are willing to test it. It would help us figure out if there is something that needs to be done before release 🙂
Please let me know!
Hi Paul Johan, thank you for sharing the info about the slowdowns. We’re looking into it right now and I’ll come back to you as soon as we find something.
Hi, sorry that is not supposed to happen… I’ll have to check what is going wrong with posting code on the forum.
In the mean time, please send your files to support@status301.net
Hi Bob, yes you can initiate a light box with iframe content from a link or button.
1. First, activate the iFrame option on Settings > Media. Once activated you may modify preferred light box sizes if you need to.
2. Then go to edit the page, post or the sidebar where you wish to create your link or button.
3. Insert an HTML block or widget and paste the following code:
<a href="#" class="fancybox-iframe button">LINK TEXT</a>4. Replace the # in the href attribute with the URL that you would use in a normal iframe embed (the src attribute) and the LINK TEXT with whatever text you want to appear.
Save your post/page/widget and test 🙂
Note that the class “button” was added in the hope that it is a class that is defined in your theme stylesheet. If it’s not, you can open your theme Customizer and define it yourself in Custom CSS. See button example.
Good to hear that worked!
There is a button “Donate to this plugin” on the right side of the free version plugin page https://wordpress.org/plugins/xml-sitemap-feed/ … Thanks 🙂
The PUM div has
z-index: 1999999999so if you give the FancyBox z-index one more extra digit (like a 9) it should start working 🙂Hi Bob, you could try changing the Z-index for the Easy FancyBox light box to a higher level. I’m not sure how high it needs to be to show before the Popup Maker light box but try adding this in the Additional CSS field in your theme Customizer:
#fancybox-wrap { z-index: 1111101; }Hi Edoardo, you are not the only one encountering this problem. The Publisher Center Help forum is full of threads about it. And not just for WordPress sites. Some report that the issue “just went away” after a while, some in days, some only after months.
Although Google does not give one clear answer (and in a recent Publisher Center Help update a dedicated page on this issue seems even to have been deleted!) I’ll try to explain what I suspect Google News does, based on several sites and experiences, and what you can do to get it sorted.
First: this should not be related to your Google News sitemap. GN has said it does not retrieve image / thumbnail information from the sitemap. It uses its own algorithm to find the best suitable image from two possible sources: the RSS or Atom feed(s) you added in your Publisher Center, or the Post content/source code itself. Or both of these, depending on your settings in Publisher Center.
Second: Google News may even discard images that are clearly marked as “featured”, because it may be an incorrect size/orientation or show inappropriate content. I suppose this last reason for not using an image is very rare though, but the size/orientation reason is common. Minimum is said to be 60px by 60px so GN can make at least a thumbnail from it, but preferably larger and in landscape format to use it as full-width header image on different news outlets. Even though you cannot force GN to use full-width image layout, it’s best to provide such an image if possible. Specially if you are using AMP pages, then you’ll need images of at least 1200px wide!
What you can do to make sure Google News finds the correct image:
1. Make sure you give your news posts a featured image of a fairly large size.
2. Verify if featured images are marked as such in your page source code. Open a post in your browser, press Ctrl+u to view the page source. Press Ctrl+f and enter
og:imagein the search field. If you find an entry like<meta property="og:image" content="..." />then verify if the URL in the content attribute is the correct image. (Note: I’m not sure if external CDN domains — like https://i2.wp.com/yoursite.com from Jetpack for example — are allowed by GN). But if there is noog:imagepresent, then you can use any SEO plugin (or Jetpack with the Share module) to add one.3. Verify if featured images are present in your RSS/Atom feeds. Specially if you have added feeds for sections in your Publisher Center. You can use a plugin like https://wordpress.org/plugins/featured-images-for-rss-feeds/ to add featured images with the correct markup so they will be recognized as thumbnail image.
4. Ask Google News to look further than just the feed. In your Publisher Center, under the Content tab, you will see your Sections listed. Each should have a feed set up as source. Click Edit and scroll down to Feed options. By default, the option “Generate articles directly from feed” will be selected. Change this to “Generate articles by crawling source URL” or “Generate articles directly from feed and crawl”.
Hope this helps 🙂
By the way, the next Google News Advanced plugin release will provide a dedicated RSS feed that includes featured images…
but now on desktop is aligned on left…
Yes, that is what I meant with “Changing it through CSS will move the frame out of center position, leaving a larger margin on the right side.”
What you could do is bypass the 20px minimum limit on your Settings > Media admin page by doing this:
1. Go to Settings > Media and find the field Margin in the Window > Appearance section.
2. Right-click the input field and select “Inspect” (or similar, it depends on your browser)
3. In the developer tool box that now opens (usually on the right side) you will see the part of the page source code that matches this input field. It should look like this:
<input type="number" step="1" min="20" max="80" name="fancybox_margin" id="fancybox_margin" value="0" class="small-text">
4. Change the element attributemin="20"tomin="0"by double-clicking it and then manually removing the2, then hit the Enter key.
5. Now back on the settings page itself, you can lower the Margin to 0
6. Hit the Save Changes button at the bottom.
7. Remove the style rule#fancybox-wrap { padding: 0 !important; left:0 !important; }because that will only confuse the script.Now you should get a better result…
Hi Eugenio, are you talking about the space between the light box frame and the edge of the browser window? This is calculated on the fly by the light box script. You can reduce it to 20 pixels but lower than that is prohibited because it will partially hide the close button and (depending on theme CSS) force the site width to surpass browser screen width, adding a horizontal scroll bar.
I’ve put up an example on https://demo.status301.net/ if you click the link Google Maps “embed test” you will see the result.
Changing it through CSS will move the frame out of center position, leaving a larger margin on the right side.
The best approach to fully cover your site, is to set the Margin to its lowest value (20px) and then set the Overlay to have Opacity: 1, and Color: #FFF or another color that matches either the embedded site or your site background color…
Hi Eduardo, thanks for confirming!
Apparently, forcing the Status response to 200 is enough. I’ll work that into the next release so you won’t need to do this edit again after updating the plugin.
If you ever find out why this 404 response occurs or where it is coming from, we’d really like to know 🙂
