Renee Johnson

@moshiphoto thanks for reaching out!

When I view the details of the theme, I’m not seeing stated AMP compatibility. This means that theme may be adding restricted code/ markup on AMP pages (see the AMP specification).

The plugin automatically removes this markup in order for the pages to pass AMP validation, which may lead to some visual changes like the one you are describing. It looks like you are using Standard Mode which serves the site as fully AMP. I recommend switching to Reader Mode (and one of the Reader mode themes), which serves a different theme for your AMP pages alongside your non-AMP pages. You’ll then still get the speed and benefits of AMP in this mode.

If you’re aiming to serve your site as fully AMP, you can inquire with the theme author if AMP compatibility is on the roadmap. You can also explore AMP-ready themes and plugins on our Ecosystem page.

@nicowebmaster thanks for your reply!

So it appears the free version of Astra since version 3.0 ships with a new header and footer builder. In testing this feature, I can change the menu without issue, but I do encounter a problem when trying to expand/collapse the hamburger menu (video). We’ll be reaching out to Astra about this.

Are you using this builder for your menu or have you built the menu with some of the Astra Pro addons mentioned in this article? If the latter, note that Astra may not support these on AMP pages at this time.

@hornback2019 no problem at all! Feel free to let us know if you are able to proceed.

@ziadmasry from what I know of the issue, AMP is working properly but there could be a restriction placed by the country from where you are connecting. From my geographical location, I can see all the elements that are missing in your view and I do not have the console errors.

@imran_kanjoo thanks for your topic!

While this may be a question for Search Console Help, note that these areas of the Index Coverage report indicate the following in the documentation:

Alternate page with proper canonical tag: This page is a duplicate of a page that Google recognizes as canonical. This page correctly points to the canonical page, so there is nothing for you to do.

Discovered – currently not indexed: The page was found by Google, but not crawled yet. Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl. This is why the last crawl date is empty on the report.

So it looks like Search Console has detected both the non-AMP and AMP URLs, but indexing is pending (which may take some time).

@ziadmasry thanks for providing these screenshots! From the console errors, it looks like you may be encountering a block on AMP scripts which may be related to your geographical location. From similar reports, other users have been able to bypass this restriction with a VPN service.

@hornback2019 thanks for the info!

When I check the source code of your site, it looks like the Exact Metrics plugin is adding the tracking code (screenshot).

Note you can continue to use this method to connect to Analytics and make use of Site Kit’s data dashboards, but the Google Account you’re using with Site Kit needs to be granted administrative permissions for the property to bypass this error.

You can also choose to have Site Kit insert its snippet by removing this tracking code on your site and toggling on the option to Let Site Kit place code on your site under Site Kit > Settings > Analytics > Edit.

@hornback2019 thanks for reaching out!

Are you receiving a specific message from Site Kit when you try to go through the set up process or connect any of the services?

If so, please share the message and your site URL. We’d be happy to assist.

@ziadmasry thanks for your reply!

Could you check for any browser console errors on the page where the elements do not appear?

@nicowebmaster thanks for reaching out!

While the Astra theme has compatibility with AMP, you may want to read this article about features that may not work in AMP due the use of code that is restricted on AMP pages (AMP specification). Elementor currently isn’t AMP compatible, but we’ve reached out to them about improving it.

The AMP plugin will automatically remove invalid markup to ensure AMP pages are valid. When I view your AMP URLs currently, I do not see validation errors, however the plugin’s internal tool may be picking up and removing the invalid markup. To identify which theme or plugin is involved, navigate to AMP > Validated URLs and look at the Sources column which flags where the invalid code originates.

I do not have the possibility to choose the AMP menu … suddenly it is not practical;

Could you confirm which version of Astra you are using? On my test site, the default menu works on AMP pages (video).

@ziadmasry thanks for your reply.

Could you try to view the page in an incognito browser window? This could rule out if browser extensions are involved.

@calgarytech thanks again for your report! We’ll be looking into fixing this. Also, as you have replied, the ongoing connection should be fine. The issue is experienced at initial connection of the Adsense module.

• This reply was modified 3 years, 10 months ago by Renee Johnson.

@izzymead thanks for your topic!

While I don’t see Site Kit activated on the site currently, I do see the referenced snippet for the tracking ID being flagged in the source code.

Checking the settings of your theme or plugins are good places to look for this code snippet. Also, checking the header.php file of your theme to see if it has been manually placed is another location.

Let us know if you are able to locate it.

@zeytin2002 thanks for your topic!

I think I spot the potential issue when checking the rest route for your site. In your WordPress Settings (under Settings > General from the WP admin dashboard) could you ensure the WordPress Address reflects the full URL where your admin pages reside (is there a www prefix?)?

@comicschau thanks for this information and I can certainly understand the endeavor. Standard mode is what we hope everyone can achieve, however if your theme and plugins are not currently AMP compatible it may take some steps to get there.

From what I can tell, the Gridlove theme, WP Review and TotalPoll Pro plugins do not state AMP compatibility. So there is a possibility that they can add invalid markup (like custom JavaScript) or affect CSS limits (75kb limit) which are some of the restrictions in the AMP specification. WP Disqus also doesn’t state automatic AMP compatibility, however there are some manual examples of how to configure it available on their Github repository (example one, example two).

Using the Plugin suppression feature may help if the invalid aspects on AMP URLs originate from a plugin. Additionally, the plugin has an internal validation tool which automatically removes invalid markup from AMP URLs by default. Note that this may result in visual and perhaps functionality differences from the original URLs when using Standard and Transitional mode since code is removed to ensure a valid AMP page is served. You can also choose which pages are served as AMP in the settings (by content/ template type) and on individual pages in the editor.

If you are aiming towards Standard mode, but are not sure of the compatibility status of your theme or plugins I recommend the following:

1) Inquire with the authors of your theme and plugins to see if they currently have or are planning to add AMP compatibility.
2) Check the Ecosystem page to see if there are potentially other AMP compatible options you can use.
3) If you would like to experiment to see how your site works with AMP, you can try Transitional mode which will still serve the original site along with an AMP version. That way you can evaluate the AMP version to see what the validation tool says about potentially offending markup.

Then you can plan a path toward serving your site as fully AMP.