Google Search Console reporting errors

Debugging works by adding #development=1 to your AMP url and to then check your developer console. Here you can see the following error is reported for your page:

https://serienfuchs.de/news/orange-is-the-new-black-staffel-3-broadway-im-gefaengnis-2-1015/amp/:248:0 The attribute ‘align’ may not appear in tag ‘p’.

That’s this line:

<p align=”right”><i><small>Beitrags-Bild: Darla Mack @ Flickr; CC BY 2.0 </small></i></p>

Are you on the latest plugin version? I think align should be stripped, at least from div tags, not sure also on p tags already, else the devs are likely going to pick this up!

Thx for your answer, Omeprazol.

I could fix the problem with the align.

Do you have any idea why the images aren’t displayed on my AMP sites? Why is the site logo (https://i0.wp.com/serienfuchs.de/wp-content/uploads/2015/01/serienfuchs-logo_512x512px-54c6331dv1_site_icon.png?fit=32%2C32) marked as schema.org <img> and not the uploaded article image?

Is this caused by the not optimized image size 640×400 px. Required width is at least 696px…?

For me are different errors..

AMP validation had errors:tx.error @ cdn.ampproject.org/v0/validator.js:320
cdn.ampproject.org/v0/validator.js:320 https://anton.com.mx/2016/02/televisa-lanza-plataforma-estilo-netflix-claro-video/amp/:218:123 The attribute ‘rel’ in tag ‘a’ is set to the invalid value ‘no’.tx.error @ cdn.ampproject.org/v0/validator.js:320

https://anton.com.mx/2016/02/televisa-lanza-plataforma-estilo-netflix-claro-video/amp

Thank you in advance for your help.

Note that our sites are all working with our default size of 500×375 images (we’re going up to 600x soon). So, you don’t have to make image 640x … that is just “suggestion” vs having 250×250 boxes or something old school. ??

We do also use 640xNNN images on one site, and those work also. But no problem with 500×375 images.

Actually even smaller images show up on the AMP page if “inline” in a story.

However, note we are loading our images locally vs off CDN or wp.com

how did you fixed the align issue?

It’s happen to me on plenty of articles and its the default wordpress editor that’s sets the align on <p> tags.

When we choose to align on the editor align buttons, those align tags are used.

many thanks.

@therethere: in our case it wasn’t an issue of the default wordpress editor. we just had to remove the align attribute in the <p> tags. Couldn’t you overwrite the HTML in the text version of an article?

I am having the align issue on <p> tags too. I can edit it but I have got tons of articles with them. Is there any way to fix it by functions.php?
Thank you very much!

Best way to fix the align tags is global search/replace in the mysql dbase and replace with centered text class.

A WP dbase editor plugin might be able to do that, but have not yet tried it (on the to do list …) — making sure to do full backup first.

Also for images, the plugin only renders what is “in the post” — so a ‘featured’ image loaded into a theme layout as a background image or “outside” the post, won’t render in the 0.3x version of the plugin. So, you need to edit the template to pull in the featured image the same way your theme template does.

The YOAST SEO + Glue plugins will setup the porper header for a featured image, but doesn’t insert it (*the actual image*) into the amp teamplate.

It’s not a job, it’s an adventure! ??

for the align tags ….

I am going to try this plugin just to see if it works for this, although I know how to do it via phpmyadmin, it might be more convenient :

https://www.ads-software.com/plugins/better-search-replace/

(MAKE BACKUP OF YOUR MYSQL DBASE BEFORE TOUCHING IT!)

I can replace all the align right but every new post will have it since it’s the default wordpress editor that is assigning paragraph with align rights

Yes, well, stop doing that ??

There should technically not be *any* inline styles in modern HTML.

Meaning, you should only be using classes and not writing HTML in the post.

This has technically been “wrong” for WordPress to default to that the past several years, but it makes things compatible with all web browsers, including old/insecure/hackable ones like old IE, early Chrome, old FF, etc.

Ideally you should NOT use the alignment options in the post editor — I am looking right now for a hook to over-ride the default behavior in the WP post editor to instead you a CSS class — but have not yet found one (hint – would make a good plugin).

Also I have not yet tried the “sanitize” function in the AMP plugin — potentially that could rewrite the align tags to classes? Dunno.

Obviously you have to actually create the CSS3 classes and put them into your style.css or custom-style.css or whatever for your site/theme — or appropriate theme panel or plugin methodology you might be using.

example custom css

p.paracenter {text-align: center;}
p.paraleft {text-align: left;}
p.pararight {text-align: right;}

<p class="paracenter">This would be centered text in a post</p>

In the past I’ve seen some funky stuff with trying to assign alignment classes to paragraphs in the WP post editor, so obviously best to do that in the text editor, vs visual editor.

If your theme already has CSS alignment classes created, you can obviously use those. Don’t use shortcodes for alignment.

Hope that helps!

(admin, feel free to add any of my rantings from the forums here to a FAQs page! –Chris S.)

Will Google reject those amp pages with the align parameter? Or will it accept even if they have those errors?

Go to your Search Console account, go to the error listings for AMP, and inspect one of the errors …

if a page is listed as “error” and not “indexed” and one of the ‘error’ pages has the align tags, I think the answer is self evident.

Try editing one of the error pages, then later go back and retest to see if is no longer listed in the errors and has move to the indexed category.

Also worth reading Google’s docs, information and the dedicated website for AMP to better see what the “requirements” are — if a page doesn’t meet the requirements, it doesn’t get indexed as amp-compatible, since it’s not.

Remember, this only impacts whether or not Google will serve the faster AMP version to a mobile user over normal optimized responsive version that you should have already optimized for best possible Google PageSpeed Insights for mobile score.

And, if “compatible” it will also get a little lightning bolt in SERPS for mobile in place of “mobile friendly” or whatever it says now. This helps folks on a train, know the page won’t burn through their mobile bandwidth with a 2MB packet of crap.

??