pagefrog
Forum Replies Created
-
Forum: Plugins
In reply to: [Facebook Instant Articles & Google AMP Pages by PageFrog] FIBA empty bosyHi fspagnuoloostfeld,
You’re absolutely right. The empty body issue was actually resolved for AMP, but the empty body issue for FBIA is still being fixed.
Forum: Plugins
In reply to: [Facebook Instant Articles & Google AMP Pages by PageFrog] Adsense formatsIf you have multiple AdSense accounts, make sure it’s hooked up to the right one. I personally have a lot of Google Accounts so I do get them mixed up sometimes.
Other than that, super tall skyscraper ads aren’t supported, super wide banner ads aren’t supported, but anything resembling the ratio of a square should work. Especially if you have a responsive ad in the account, that’ll definitely work.
So my best guess is to make sure it’s the right Google Account that’s connected!
Hi jef3000,
Currently, AMP only supports the following analytics platforms:
Adobe Analytics
AT Internet
Chartbeat
comScore
Google Analytics
LiveInternet
Parse.ly
Quantcast
SimpleReach
TNS
Webtrekk GmbHAll of the above are currently supported in PageFrog, but we cannot build support for any additional platforms until Google allows it.
You can certainly use the “#development=1” to validate an AMP page, but it’s important to note that AMP validation is only one of the many rules Google Webmaster Tools requires to actually index the AMP page.
For example, #development=1 will only report any AMP errors, but Google indexing will also check schema errors as well.
Long story short, just because #development=1 shows that the AMP page is valid, it still doesn’t mean that Google will index the page.
Another tool that could come in handy is Google’s Structured Data Testing Tool which will help you identify any schema issues https://developers.google.com/structured-data/testing-tool/
Sorry for the late response. Somehow I never received notifications for a few threads. I’m finding them now here and catching up on all missed questions.
We push a big update earlier today that should solve the /amp/ issue. Could you update PageFrog and try again?
Sorry for the late response. Somehow I never received notifications for a few threads. I’m finding them now here and catching up on all missed questions.
Currently the only ad platform we support is AdSense for AMP. We plan to add support for additional ad platforms very soon along with the ability to insert your own action bars and call-to-actions.
Right now we’re focusing on helping users resolve AMP errors so that pages can be properly indexed. Once this phase is stable, we’ll move onto building additional integrations for various analytics and ad platforms, along with a lot of branding and customization options as well.
I’m so sorry for the late response! I’ve been receiving hundreds (maybe thousands!) of emails and this one seemed to have slipped through the cracks.
We push a big update earlier today that should solve your logo upload. Could you update PageFrog and try again?
Hi Surgbug,
I’m so sorry for the late response! I’ve been receiving hundreds (maybe thousands!) of emails since AMP rolled out. I’m doing my best to keep up with all the questions and requests.
We did indeed push a big update earlier today v1.0.9 that should solve the issue you outlined above. Could you update PageFrog and try again?
PageFrog actually supports Pages, so everything should already be working.
Hi andyafflect,
The duplicate images issue was resolved for AMP, but the fix for FBIA has not been released yet. AMP and FBIA operate independently, so we usually resolve their respective issues separately as well!
We’ll get this into an upcoming update asap. We release major updates every 2-3 days, so it shouldn’t be long!
For anyone else experiencing issues regarding a blank page, these errors are usually caused by PHP errors. If you could share with me your PHP error log, that would help me solve the issue.
For those unfamiliar with generating PHP errors logs, here’s a plugin that makes it really easy to generate PHP error logs https://wordpress.org/plugins/error-log-monitor/
Once you get a list of PHP errors, please send them to me here or at team@pagefrog.com!
Hi thetafferboy,
Google Authentication requires outbound HTTP requests, so if you have any server configurations or plugins that’s preventing outbound HTTP requests, then that would be blocking your site from communicating with Google’s Authentication services.
If you could share the list of plugins you have installed, I may be able to help you identify which one could be preventing the requests from going through.
Hi DKornyukhov,
Mike from PageFrog here—happy to help!
There shouldn’t be any issues. PageFrog works in the backend so it shouldn’t matter where the posts are submitted.
If you run into any trouble, just let me know and I’ll be sure to fix it for you. You can write on the support forum here at any time, or feel free to reach me at team@pagefrog.com as well.
Hi thetafferboy,
Yes, we most definitely do plan on adding share buttons very soon! I will let you know when we roll that feature out.
I know our plugin isn’t perfect yet, but if you appreciate our work, please take a few seconds to give us a 5-star on the WordPress store here https://wordpress.org/support/view/plugin-reviews/pagefrog
Thank you so much!
Hi NPU,
The 250 word limit is more for longer blogs to ensure you don’t have too many ads after one another. But if your article has less than 250 words, you will still have 1 ad at the end!
Hello everyone,
Breaking news!! We’ve identified and resolved all the issues mentioned here regarding permalinks. There was an issue where the “amphtml” tag was not pointing towards the right AMP url, which caused a lot of issues.
The new 1.0.9 update includes a fix for this so that the “amphtml” tag will always point towards the right AMP url. Most of the issues mentioned here should be resolved.
Please try it!