pagefrog
Forum Replies Created
-
Hi taniav,
Rest assured, the categories and tags are not removed on a functional level, they’re simply hidden from display. This was primarily a design choice we made (and we had to make a lot of them when we first started!)
The goal of AMP (and Instant Articles) is to remove clutter and create a superior mobile reading experience. One of the things that cluttered mobile screens were excessive use of tags and so we decided to hide this, allowing readers to focus on the content.
However, we’re slowly adding back customization options so you can expect to see the option to display tags and categories in the near future.
Also gooma2,
I’m happy to share that your issue has been resolved! We identified the problem which was a result of the “amphtml” tag pointing towards the wrong AMP url. This has been fixed and I’m confident that your pages, both old and new, will be indexed appropriately with the new 1.0.9 release.
Hello gooma2 and paul buxbaum,
Breaking news!! We’ve resolved the permalink issue and it should definitely fix the issues you saw regarding AMP indexing.
Previously, there was a discrepancy between where the “amphtml” tag was pointing towards, and where the AMP pages actually reside.
We’ve resolved this error so that the “amphtml” tag is always pointing towards the appropriate AMP url.
This fix has been included in 1.0.9 which we just released.
Hi Der-Bank-Blog,
This has been resolved for AMP but not yet for IA. We’ll be applying the same fix for IA in our upcoming update! We’ve been releasing major updates every 2-3 days, so you can expect a fix for this soon.
AMP and IA operate quite differently, so often times their issues are resolved separately.
Thank you bmg1227 for pointing towards the other thread!
I’ll echo the response here for other readers to see:
We just released an update to the plugin that prevents duplicate images from showing as the featured image! You can also disable featured images on AMP altogether under Mobile Formats > Settings at the bottom of the page you’ll find a checkbox.
In other words, the duplicate image issue should be resolved, so no action is necessary. If you’d still like to disable the featured image, you can do so under the Settings page!
Thanks andyaffleck and newzdotit,
We’ve identified the issue causing blank IA posts! We’ll include a fix for this in our next update. We’ve been releasing an update every 2-3 days, so you can expect this resolved very soon.
Hi dannybrown,
bmg1227 is right on this one, the Search Console only updates when Google crawls your site. Google has stated that it could take up to 7 days for AMP pages to be indexed.
Keep me posted and let me know when your pages have been indexed by Google!
[resolved]
Hi madmaxy,
The current version of the PageFrog plugin is built on top of the AMP plugin by Automattic. PageFrog adds additional functionality to the core AMP plugin such as analytics, ads, styling, etc.
To make full use of PageFrog features, you’ll need both the PageFrog plugin and the AMP plugin installed, activated, and updated.
Hi Chukwudi,
Great! Glad to hear that the Force AMP Compliance option worked. If you encounter any other issues please feel free to write them out here, or email me at team@pagefrog.com 🙂
Hi gattoplatone,
Mike here from PageFrog—happy to help!
AMP errors are most often caused by some of the plugins you’ve installed. Most older plugins are not AMP compatible, so you’ll get a lot of errors. In this instance, it would appear that ContentEgg is not yet AMP compatible, so it’ll do all sorts of weird things.
If you update to the latest version of PageFrog, you’ll find a new feature called “Force AMP Compliance” which will disable conflicting plugins on AMP pages to avoid these errors. You’ll find this under Mobile Formats > Settings, it’s a checkbox near the bottom of the page.
Could you try that and let me know the result?
Hi gooma2,
Thank you for taking the time to write this message and to help many other users on this forum. We’re working as fast as we can, all hands on deck, to investigate this redirect bug.
Any information, error logs, or observations anyone can provide us will drastically speed up our progress on resolving this issue.
So far, we’ve seen this happen to URLs ending in .php and .html, which is a starting point. We’ve also seen it working properly with .php and .html as well, so it’s at the very least an area worth investigating.
With PageFrog and WP AMP plugins installed, the original page should include an “amphtml” tag which tells Google where the AMP page is. We’ve seen that this code is pointing Google to /amp, but for some pages the AMP page is living on ?amp=1.
This is because /amp doesn’t work with all permalink settings. For example, http://example.com/?p=N/amp would not work since the /amp is appended after the ?.
These are our discoveries so far and I’ll share our progress as we move along. This is our top priority at the moment and we’ve resolved several major bugs in the past relatively quickly, so I’m confident we can do the same with this one.
We have been releasing major updates every 2-3 days to help publishers get on AMP as soon as possible. We’ll keep up this release schedule so please keep reporting any errors and bugs to us on the forum here or by email at team@pagefrog.com.
No problem! If you have any other questions, feel free to write on this forum or reach me directly any time at team@pagefrog.com 🙂
Right now it’s either logo or text, not both. However, I agree it’s important to have this flexibility so I’ve added it to our list of features to work on.
Hi Seph,
In our latest update, we removed the “by” in the author since it was causing complications with different languages. Now it should just show the author name.
As for the issue with the title, could you show me a link to your page? If I can see it, then I can inspect the code and see what’s going on.
Forum: Plugins
In reply to: [Facebook Instant Articles & Google AMP Pages by PageFrog] Logo very smallHi Seph,
The AMP bar will fit in the entire image you upload, so if there’s a lot of blank space around the graphic in the file, then that could be what’s making it appear small.
Could you send me a link to this file of yours? Also feel free to send it to me directly via team@pagefrog.com.