Viewing 8 replies - 1 through 8 (of 8 total)
  • Thanks for reaching out. Firstly it looks like you have multiple plugins that are not AMP compatible, with no AMP version of those URLs available at present. Do you have all supported templates AMP enabled? If so please share your Site Health information here or privately via this form and we’d be happy to check your current setup.

    In relation to loosing views it looks like your using Google Tag Manager to insert your Analytics tracking snippets. Can you confirm you’ve published your both your web container (for your non AMP URLs) and your AMP container (for your AMP URLs), with a Universal tracking tag in both? I couldn’t see any Universal tag (UA-) reference when checking your site and Tag Manager containers.

    Thread Starter enricobt

    (@enricobt)

    Hi James,
    I have all AMP templates enabled with the exception of pages as I have home page developed via Elementor, that is not compatible with AMP.
    But this should not be really a problem, as I have only a dozen of pages while my blog hosts more than 3.000 articles.
    Regarding TAG manager, we installed a separate container for AMP pages via the AMP Google TAG Manager plugin:
    https://gist.github.com/westonruter/2ea25735be279b88c6f0946629d0240c
    The container is: GTM-NKDQXZV
    While the standard container is: GTM-5KZ7M6N.

    Then I filled up the form where you can find more details on my overall WP configuration.
    Regards
    Enrico

    Thread Starter enricobt

    (@enricobt)

    Hi James,
    I reviewed again the AMP configurations as you suggested, so now we have AMP enabled in all templates, with the exception of HomePage, to keep it editable by Elementor.
    Please see this screenshot:

    View post on imgur.com


    Regards
    Enrico

    Many thanks for the update. As you have all your supported templates AMP enabled let’s perform some additional troubleshooting steps to see why first of all there is no AMP version available. As you have a couple of optimization and caching plugins active please try the below:

    1. Ensure your already installed Health Check & Troubleshooting plugin is active
    2. Navigation to your “Plugins” screen and click on the “Troubleshooting” link next to the AMP plugin.
    3. Open an AMP URL where there is no AMP version available yet, such as this one.
    4. Check if there is an AMP version available (via the admin toolbar)
    5. If not open that page for editing and share whether you have this specific page AMP enabled
    6. If there is an AMP version available this may an indicator that a theme or third-party plugin is resulting in this page not having an AMP version available. To troubleshoot hover over the “Troubleshooting Mode” icon and enable your active plugins, one by one. Each time you activate a plugin while in troubleshooting mode the page will reload. Check for the same issue each time.
    7. If at any stage there is no AMP version available let me know which plugin you activated for this to occur.

    In relation to your Tag Manager issue and Analytics not firing we can investigate this from a new support topic to see what’s occurring.

    Thread Starter enricobt

    (@enricobt)

    Hi James
    actually, all these URLs that starts with:
    https://magazine.lorenzovinci.it/page/….
    and have a number and the end, i.e:
    https://magazine.lorenzovinci.it/page/175 or https://magazine.lorenzovinci.it/page/123
    etc..
    do not exist either in AMP enabled or in AMP disabled versions. And all of them point to site homepage.

    So I don’t really have any idea where these URL are coming from.
    The only thing is that Googlebot for smartphones found all them and they have been listed and marked by Google Search console, only with AMP extension, by a server error 5xx that is a real error because the page doesn’t exist.
    Regards
    Enrico

    Ah, I see. In that case they could be historical URLs that no longer exist, resolving instead to your homepage. With newly pages all having an incremental ID some of your older ones may have been since deleted. From checking these non existent pages may also be from previous sites before migrating, I noticed a backup and restore plugin.

    Also from checking your page sitemap the URLs I checked all seem to have AMP versions available.

    You may also find the Index Coverage Report useful, a Search Console tool. The issue isn’t specific to the AMP plugin and is more Search Console related.

    Feel free to open a new support topic in relation to your Analytics not firing and I’d be happy to assist.

    Thread Starter enricobt

    (@enricobt)

    Hi James,
    you are right, I found that these archive pages are coming from my previous theme.
    When I switched to NEVE, first I did it by changing only mobile (AMP in reader mode) then, after 3 mounths, I completed migration by changing desktop theme too (AMP in transitional mode now).
    But, at the end all desktop pages went away, while these AMP pages remain in Google Search console with server error 5xx.
    I suspect that these may be cached in AMP Google cache, but I am sure how to clear all of them.
    Moreover, I tried to use 301 Redirect on a couple of them, but it seems that 5xx server errors occur before redirect. On other side I don’t know why they go ultimately always to home page, instead of going to 404 error page as page doesn’t exist.
    Do you have any idea on how to clear out these 5xx errors?
    Regards
    Enrico
    PS: via Google Tag assistant, I see that I transmitting both UA- of my site, see attached screen shot.
    https://imgur.com/o3hy48E

    Thanks for your reply. For posts or pages that no longer exist I suspect these will be eventually removed when your site is re-indexed. If there are internal references to these non existent links there may be plugins that can assist in locating and correcting these links.

    PS: via Google Tag assistant, I see that I transmitting both UA- of my site, see attached screen shot.

    The references from your screenshot seem to indicate different views, although the same Analytics property.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Google Search console errors’ is closed to new replies.