Loading the report…
Loading the report…
An independent audit of ampproject.org, measured by Adnave on November 13, 2026. We read 12 pages of the site as a search engine first receives them and ran 53 checks. Organic health is 81 out of 100. The site lets the main AI assistants read it.
Growth Navigator · amp.dev
16 opportunities to improve
12 pages read in full, 30 more links checked
Organic health
out of 100
Ads readiness
out of 100
Our suggested order: biggest obstacles first, quickest first among equals. The effect of each fix is not measured. 3 take minutes.
Step 1 · Organic
Everything here was observed on the site. Fixing it removes a known obstacle; no one can promise a specific ranking in return.
Observed · AdnaveBot's reading of 12 pages on 2026-11-13 · each finding is what we saw on those pages; “what to do”, the score and the order are our judgment
These addresses are linked from your own pages but return an error. Visitors hit a dead end and search engines waste their visit.
What to do: Fix the link, restore the page, or redirect the old address to the closest live page.
Google will choose its own snippet for these pages, often a poor one.
What to do: Add a description of 70 to 160 characters to each page.
“AMP - a web component framework to easily create user-first web experiences - amp.dev”. Titles outside roughly 30 to 60 characters are either vague or get cut off in results.
What to do: Rewrite it to 30 to 60 characters, leading with the main thing people search for.
How to fix this: How to write page titles and meta descriptions“Whether you are a publisher, e-commerce company, storyteller, advertiser or email sender, AMP makes it easy to create great experiences on t…”
What to do: Aim for 70 to 160 characters so it is specific but not cut off.
How to fix this: How to write page titles and meta descriptionsWhen someone shares the page, the preview will look bare or use the wrong image.
What to do: Add Open Graph tags: og:title, og:description and an og:image of 1200 × 630 pixels.
Paste inside the <head> of the page. Replace the image address with a picture of 1200 by 630 pixels.
<meta property="og:type" content="website"> <meta property="og:title" content="AMP - a web component framework to easily create user-first web experiences - amp.dev"> <meta property="og:description" content="Whether you are a publisher, e-commerce company, storyteller, advertiser or email sender, AMP makes it easy to create great experiences on the web. Use AMP to build websites, stories, ads and emails."> <meta property="og:url" content="https://amp.dev/"> <meta property="og:image" content="https://amp.dev/your-preview-image.png"> <meta name="twitter:card" content="summary_large_image">
A page should have one H1. Several of them blur what the page is about.
What to do: Keep one H1 and turn the others into H2 subheadings.
How to fix this: How to write page titles and meta descriptionsA single H1 tells search engines what each page is about.
What to do: Give each page exactly one H1 that states its topic.
A sitemap lists every page so search engines find them all, including new ones.
What to do: Generate a sitemap.xml and submit it in Google Search Console.
Save as sitemap.xml at the top level of the site, then submit https://amp.dev/sitemap.xml in Google Search Console. It lists only the pages this audit read; add the rest.
<?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <url><loc>https://amp.dev/</loc></url> <url><loc>https://amp.dev/about/websites/</loc></url> <url><loc>https://amp.dev/about/stories/</loc></url> <url><loc>https://amp.dev/about/ads/</loc></url> <url><loc>https://amp.dev/about/email/</loc></url> <url><loc>https://amp.dev/about/how-amp-works/</loc></url> <url><loc>https://amp.dev/about/mission-and-vision/</loc></url> <url><loc>https://amp.dev/about/use-cases/</loc></url> <url><loc>https://amp.dev/success-stories/</loc></url> <url><loc>https://amp.dev/documentation/</loc></url> <url><loc>https://amp.dev/documentation/guides-and-tutorials/</loc></url> <url><loc>https://amp.dev/documentation/components/</loc></url> </urlset>
Only 0 H2 subheadings found.
What to do: Break the page into sections with H2 subheadings that use the words people search for.
How to fix this: How to write page titles and meta descriptionsA field with no label is announced to screen-reader users as just “edit text”, and placeholder text disappears as soon as someone types. Clear labels also raise form completion.
What to do: Give each field a <label for="its-id">, or an aria-label if the design has no room for visible text.
An icon-only link or button with no text is invisible to screen readers and tells search engines nothing about where it leads.
What to do: Add an aria-label saying what it does, for example aria-label="Open menu", or alt text on the image inside it.
hreflang tags tell search engines which language version to show each searcher. A set that leaves out the page itself, or the fallback, is often ignored as a whole.
What to do: List every language version on every page, including the page itself, and add one x-default entry for everyone else.
This small file tells search engines what they may crawl.
What to do: Add a robots.txt at the root of the site that allows crawling and names your sitemap.
Save as a file named robots.txt at the top level of the site, so it opens at https://amp.dev/robots.txt.
User-agent: * Allow: / Sitemap: https://amp.dev/sitemap.xml
Assistants quote pages that state a question and answer it plainly. This page has no question-style headings.
What to do: Add a short section of real customer questions as headings, each answered in two or three sentences.
How to fix this: AI search readiness: how to be found by AI assistantsHeadings are the page's outline. When levels are skipped (a heading 2 followed by a heading 4), screen readers and search engines get a broken outline.
What to do: Use heading levels in order: one H1, then H2 for sections, H3 inside those. Style size with CSS, not by choosing a different level.
An optional plain-text summary of the site for AI assistants. It is cheap to add, but there is no evidence yet that it changes how often a site is cited.
What to do: Optionally add /llms.txt with a short description of the site and links to its most important pages.
Optional. Save as llms.txt at the top level of the site. Edit the first lines to describe what you do.
# AMP - a web component framework to easily create user-first web experiences - amp.dev > Whether you are a publisher, e-commerce company, storyteller, advertiser or email sender, AMP makes it easy to create great experiences on the web. Use AMP to build websites, stories, ads and emails. ## Pages - [AMP - a web component framework to easily create user-first web experiences - amp.dev](https://amp.dev/) - [AMP Websites - amp.dev](https://amp.dev/about/websites/) - [Web Stories - amp.dev](https://amp.dev/about/stories/) - [AMP Ads - amp.dev](https://amp.dev/about/ads/) - [AMP Email - amp.dev](https://amp.dev/about/email/) - [How AMP works - amp.dev](https://amp.dev/about/how-amp-works/) - [Vision & Mission - amp.dev](https://amp.dev/about/mission-and-vision/) - [Use cases - amp.dev](https://amp.dev/about/use-cases/) - [Success Stories - amp.dev](https://amp.dev/success-stories/) - [Get Started - amp.dev](https://amp.dev/documentation/) - [AMP Websites Guides & Tutorials - amp.dev](https://amp.dev/documentation/guides-and-tutorials/) - [Components - amp.dev](https://amp.dev/documentation/components/)
The page gives search engines real content to work with.
Alt text helps image search and screen-reader users.
No links on the page use wording like “click here”.
Without the doctype line, browsers fall back to an old rendering mode and layouts can break.
Without it, accented letters and symbols can show as garbled text, in the browser and in search results.
Search engines treat this kind of redirect as a weak signal and visitors see a flash of the old page. It also breaks the back button.
Visitors and search engines get a secure connection.
Nothing on the page blocks it from being indexed.
The page declares a mobile viewport.
https://amp.dev/index-2021/
Search engines and screen readers know which language to expect.
1 structured data block found.
Visitors who type http:// are moved to https automatically.
Both forms end at amp.dev.
A made-up address correctly returns a 404, so search engines can drop dead pages.
Browsers are told to always use the secure connection and not to guess file types.
Images, scripts and styles all load over https.
That is quick.
A reasonable size for the page itself, before images.
Scripts are loaded without delaying what visitors see.
The server shrinks the page before sending it.
Links shared on X show a rich preview.
Your icon appears in browser tabs and search results.
Nothing in robots.txt shuts out the crawlers behind ChatGPT, Claude, Perplexity or Gemini.
Structured data found: Webpage, WebPage, Organization, ImageObject.
Checked 11 other pages.
Checked 11 other pages.
Checked 11 other pages.
Checked 11 other pages.
Checked 11 other pages.
Checked 11 other pages.
Checked 11 other pages.
| Page | Response | Time | Words |
|---|---|---|---|
AMP - a web component framework to easily create user-first web experiences - amp.dev https://amp.dev/ | 200 | 0.15s | 543 |
AMP Websites - amp.dev https://amp.dev/about/websites/ | 200 | 0.04s | 1,023 |
Web Stories - amp.dev https://amp.dev/about/stories/ | 200 | 0.01s | 1,334 |
AMP Ads - amp.dev https://amp.dev/about/ads/ | 200 | 0.04s | 1,432 |
AMP Email - amp.dev https://amp.dev/about/email/ | 200 | 0.01s | 868 |
How AMP works - amp.dev https://amp.dev/about/how-amp-works/ | 200 | 0.01s | 1,358 |
Vision & Mission - amp.dev https://amp.dev/about/mission-and-vision/ | 200 | 0.03s | 770 |
Use cases - amp.dev https://amp.dev/about/use-cases/ | 200 | 0.06s | 532 |
Success Stories - amp.dev https://amp.dev/success-stories/ | 200 | 0.11s | 892 |
Get Started - amp.dev https://amp.dev/documentation/ | 200 | 0.04s | 583 |
AMP Websites Guides & Tutorials - amp.dev https://amp.dev/documentation/guides-and-tutorials/ | 200 | 0.12s | 1,238 |
Components - amp.dev https://amp.dev/documentation/components/ | 200 | 0.14s | 1,763 |
Step 2 · Ads
Ads only pay off when the site can measure what they bring in. We look for tracking tags in the page code; tags that load later, through a consent banner or tag manager, will not show up here.
Google Ads cannot learn which clicks turn into customers without it.
What to do: Create a conversion action in Google Ads and add the tag, or import conversions from Analytics.
How to fix this: What to set up before you spend on adsFacebook and Instagram ads need the Pixel to track sales and build audiences.
What to do: Create a Pixel in Meta Events Manager and add it to every page.
How to fix this: What to set up before you spend on adsTikTok ads need the Pixel to measure results and optimize delivery.
What to do: Create a Pixel in TikTok Ads Manager and add it to every page.
How to fix this: What to set up before you spend on adsGoogle Analytics is on the page.
Audit run on . It reads up to 12 pages (60 with a free account) as a search engine first receives them and checks further internal links for errors. Scores are a weighted share of the checks passed.
Run the same audit on your own site, free. No sign-up needed.
This page reports only what our audit observed on public pages of ampproject.org. Adnave is not affiliated with it. If you run this site and something here is wrong, run a fresh audit and tell us.