Google will pick that up when it crawls your site. Give it 48 hours and you can google on your mobile previously indexed urls to see if they’ve indexed they amp variant. Otherwise new indexed urls should be showing up already. Google would have cached those urls. Make sure to use mobile when you do the searching.
search.google.com
Where does the error show? In the GSC or the ampxf site? Also, what are the errors? How many errors are you getting precisely? Not all 30M posts should be affected.
Incorrect markup URL found for attribute 'href' in tag 'a'.
Yeah, I'd probably follow the GSC errors but you're right, you'll likely get the same ones in both GSC and AMPXF.Both. My guess is both consoles will produce the same errors eventually.
Example GSC error:
(Translated)
Code:Incorrect markup URL found for attribute 'href' in tag 'a'.
I only checked one post and that was indeed a dead URL.
And no, not all 30 mln posts have a dead URL but even if only 0.5% would contain a dead URL we are still talking 150.000 posts
Yes, and no
If you don't fix them, the page isn't a valid AMP page. The end result is that you're not "getting as much as you could" out of the addon if you don't fix those types of errors
@Recep Baltaş had one case with many pages, but it showed to a broken signature of one of his members, so by fixing it in one place, it resolved it in many otherAnd no, not all 30 mln posts have a dead URL but even if only 0.5% would contain a dead URL we are still talking 150.000 posts
If the case was similar as to Recep's you can request me to trigger a "mass re-evaluation" of the found pages so you don't have to click "check fix" one by one
Yeah, I think you are right.
Feel free to add your custom css using the amp css template if it that really matters to you. But since it isn’t “worth” the effort; then don’t do it.
Ok and until then you can miss out on the traffic increase this add-on offers
Ok then and until then you can miss out on the traffic increase this add-on offers
I understand your concerns
I'm sure a couple of days of due diligence won't make or break himOk then and until then you can miss out on the traffic increase this add-on offers
No but that’s why anyone would want to purchase this add-on. If he doesn’t need the traffic now or his board is private then he can hold off buying it because it’s no use for him now.I understand your concerns
At least the TH font-size problem is easily fixable (will be in the next release), and most other things can be solved, at least that is my experience.
I'm sure a couple of days of due diligence won't make or break him
Yes, that option is mostly for some old forum that has previosuly been vb and the content has a bunch of <font style="yada yada"> in it that makes the css go over allowed limit..
This is something that another customer saw also and we fixed.
@ThemeHouse maybe can comment on this:
We've noticed that the normal page has the following style set on the <html>-tag:
View attachment 243896
I don't really understand why you would inline a rule that sets font-size to be 62.5% there, unless maybe for some accessibility option?
Anyway the fix that the customer did was to change font size values in ACP to be "px" instead of "rem"
I think the "safer" way to do it would be to edit "amp_style_custom.less" to add the same :
html{font-size:62.5%}
rule.. @ichpen can you add that and report back if font sizes start looking correct?
Yes, this one can be supported, probably without a lot of extra work.
I will likely have a new release out tonight with fixes for various things
can you send me PM with a link where that happens?
