CrawlCheck

Agent view · Findings · 2026-08-14

MobileOptimized tag: on 1.65M sites, none in the top 10,000

This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/the-meta-tag-a-million-sites-have-and-the-top-ten-thousand-do-not: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.

status200
content-typetext/markdown; charset=utf-8
varyAccept
link<https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/blog/the-meta-tag-a-million-sites-have-and-the-top-ten-thousand-do-not>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory"
cache-controlpublic, max-age=900, stale-while-revalidate=2400
bytes13,901
words1,979
sha-2566220b9a07f2a4a64c2affffa81340d2c556b1cee30dbe21898aa92fbeabc2844
repr-digestsha-256=:YiC5oH8qSmTCr//6gTQNLFVrHO4w2+IYmKqS++q8KEQ=: ← matches the body shown
signature-inputsig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795183560;expires=1795187160;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="cVsbETTD4ARk4Ggmk3hZ0Q";tag="crawlcheck-page"
signaturesig1=:A2Z1qtp5KuEITV8ZSRgIrSmzrNKTXAZNPHy/njoiY3bXa31T2w4Shgt5TV7qPJCvliFZRG9xvxn/Er/M2ImcBQ==:
verifiedyes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba
Findings · 2026-08-14 · By [VSNARY | Emmanuel Orta](/author)

# MobileOptimized tag: on 1.65M sites, none in the top 10,000

A Microsoft tag for a browser that no longer exists sits on about 1.65 million sites and is still spreading, yet the top 10,000 have never carried it. Read by rank band, BuiltWith's adoption figures say the opposite of the raw count.

MobileOptimized is a meta tag Microsoft made for Internet Explorer Mobile, a browser that no longer exists. BuiltWith's figures put it on about 1.65 million live sites, and rising, but only across the whole web: in the top million it peaked around 2023 and is falling, and in the top 10,000 it has been at zero for the whole record. That pattern means templates are copying the tag, not sites choosing it. You do not need it; the viewport meta tag controls mobile layout.

On this page

- What is the MobileOptimized meta tag?
- Why does the same tag rise and fall at once?
- How do you read an adoption count before acting on it?
- What should you put on your page instead?

MobileOptimized by population, with viewport for contrast

The whole web

MobileOptimized

roughly 1.65 million live sites, rising steeply

Top 1 million

MobileOptimized

peaked near 40,000 sites in 2023, declining since

Top 100,000

MobileOptimized

flat against zero for the whole 23-year record

Top 10,000

MobileOptimized

flat against zero

Top 1,000

MobileOptimized

flat against zero

Viewport meta, for contrast

MobileOptimized

above 200 million sites, present in every band

The figures in this post are BuiltWith's, read from its published usage statistics on 14 August 2026. What we add is the reading: the same count split by site rank, which turns an apparent mandate into a warning. The method works on any technology a detection profile lists, and the tag is a clean example of why it matters.

## What is the MobileOptimized meta tag? #

`MobileOptimized` is a meta tag Microsoft introduced to set layout width for pages rendered in Internet Explorer Mobile. That browser is gone and no current browser or crawler reads the tag. Its companion `HandheldFriendly` targeted the same generation of phones.

## Why does the same tag rise and fall at once? #

Read as one number, roughly 1.65 million live sites carry the tag and the count climbs steeply. Split by rank, the lines disagree:

| Population | MobileOptimized |
| --- | --- |
| The whole web | roughly 1.65 million live sites, rising steeply |
| Top 1 million | peaked near 40,000 sites in 2023, declining since |
| Top 100,000 | flat against zero for the whole 23-year record |
| Top 10,000 | flat against zero |
| Top 1,000 | flat against zero |
| Viewport meta, for contrast | above 200 million sites, present in every band |

A technology that grows across the web while shrinking among the largest sites is not being adopted; it is being propagated. It arrives inside themes, page builders and starter templates, and the sites with the staff to notice have been removing it for years. Nobody is acting in bad faith: a template author keeps a line that once did something, and a decade later it is on a million sites.

The whole-web line also adds several hundred thousand sites within a few months in early 2026. A twenty-year-old tag for a discontinued browser does not gain users like that. A jump of that shape is one platform shipping one default to many sites at once. We have not measured which platform, so we do not name one.

## How do you read an adoption count before acting on it? #

| Question to ask | Why it matters | MobileOptimized |
| --- | --- | --- |
| Which population is counted? | A whole-web count grows with the web itself | Whole web only |
| Does the line point the same way in every rank band? | Real standards are high everywhere; fossils are high only at the bottom | Rising at the bottom, zero at the top |
| Is there a sudden jump? | Steps of hundreds of thousands are platform defaults, not choices | Yes, early 2026 |
| What does a known standard look like? | Gives you the shape to compare against | Viewport is flat and high in every band |

A detection profile lists what it can detect, which is not the same as what you should have. A count without a population cannot tell a standard from a fossil. The same reading applied to web servers is in [the web server that gained and lost 43 million sites](/blog/the-web-server-that-gained-and-lost-43-million-sites).

## What should you put on your page instead? #

If your pages declare `<meta name="viewport" content="width=device-width, initial-scale=1">`, you are done. `MobileOptimized` and `HandheldFriendly` can be removed with no change for a visitor or a crawler. The `rel="alternate"` mobile annotation is worse than useless on a responsive site, because it points a crawler at a separate mobile address you do not have.

To confirm what your page actually serves, look at the raw HTML rather than the browser's rendered view; a viewport tag can be present and still be misread, as [our own viewport check once did](/blog/the-viewport-was-there-all-along). A free scan on the [homepage](/) shows what a crawler receives.

Source: BuiltWith's published usage statistics and trend pages, read on 14 August 2026. We describe the segmented counts in our own words and do not republish their table or chart.

CrawlCheck’s dataset when this page loaded: 570,959 sites measured.

Written by

[Emmanuel Orta](/author) · VSNARY

I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post.

[Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta)

Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fthe-meta-tag-a-million-sites-have-and-the-top-ten-thousand-do-not%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fthe-meta-tag-a-million-sites-have-and-the-top-ten-thousand-do-not%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=MobileOptimized%20tag%3A%20on%201.65M%20sites%2C%20none%20in%20the%20top%2010%2C000)[Email](mailto:?subject=MobileOptimized%20tag%3A%20on%201.65M%20sites%2C%20none%20in%20the%20top%2010%2C000&body=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fthe-meta-tag-a-million-sites-have-and-the-top-ten-thousand-do-not)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)

## Questions this post answers

### Is the MobileOptimized meta tag still useful?

No. It was made for Internet Explorer Mobile, and no current browser or crawler reads it. Where it appears, it was usually inherited from an old theme or template rather than chosen.

### Can I safely remove MobileOptimized and HandheldFriendly?

Yes. Removing them changes nothing a visitor sees and nothing a crawler reads, provided the page declares a viewport meta tag, which is the tag that controls mobile layout.

### Why is a rising adoption count misleading?

A whole-web count grows as the web grows and as platforms ship defaults. Split by site rank, the direction can reverse, with the most-visited sites removing what the long tail keeps adding.

### How can I tell a real standard from a leftover?

Check whether adoption is high in every rank band. A real standard is common among the largest sites too; a leftover is common only where nobody audits templates.

### Where do these adoption figures come from?

From BuiltWith's published usage statistics, read on 14 August 2026. CrawlCheck did not measure these counts; it segmented them by rank to show how the reading changes.

### What does a sudden jump in adoption usually mean?

Usually that one platform shipped a default to a very large number of sites at once. Genuine adoption of an old tag does not add hundreds of thousands of sites within a few months.

## Related findings

[2026-10-04 402 Payment Required: what top sites send AI crawlers We read the top 1,000 sites as four AI crawlers. Three answered with 402 Payment Required and none quoted a price: a refusal, a to](/blog/ai-crawlers-get-402-payment-required-from-top-sites-none-quote-a-price)[2026-11-15 Top 1,000 websites: every outside tracker we logged We opened the 1,000 most visited homepages in a browser and logged every outside company. 685 measured; Tag Manager on 38%, Double](/blog/top-1000-websites-third-party-trackers-november-2026)[2026-08-21 Text extractors dropped our schema and still got us right Two page-to-text services for LLMs dropped every JSON-LD node we publish and still described us right. What they read, and where 8](/blog/a-pipeline-threw-away-our-schema-and-got-us-right-anyway)

The main product

Found this on your own site? **We fix it for $100.**

Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.

[Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v)
[What it covers](/pricing#fix) · [scan first, it is free](/)

Free browser extension

Check this on any site you open, **without leaving the page.**

CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.

[Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post)
[What it does](/extension)

Write for the library

Measured something yourself? **Submit an article.**

Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.

[Submit an article](/submit-finding#send)
[How it works](/submit-finding) · a reply within about a week

Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections).

## Comments

Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*.

Send for review

Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan.

[All findings](/blog) · [The dataset](/data) · [How the dataset works](/policy)

We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io)

#### How we measure, and our own machine files

CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io).

**Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing.

**Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours.

**Pages:** [Listing check](/listing-check) · [SDK](/sdk) · [Certificates](/certificates) | **Registry:** [MCP: Operator](/registry/mcp/operator) · [badmintonsoldiers.club](/registry/badmintonsoldiers.club) · [deodental.co.uk](/registry/deodental.co.uk) · [icustomer.ai](/registry/icustomer.ai) | **Glossary:** [Exact-match retrieval](/glossary/exact-match-retrieval) · [Informational query](/glossary/informational-query) · [Focus indicator](/glossary/focus-indicator) · [content-change clock](/glossary/content-change-clock) · [Encrypted Client Hello](/glossary/encrypted-client-hello)

[Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)

Same body as a file: /blog/the-meta-tag-a-million-sites-have-and-the-top-ten-thousand-do-not.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.