skyscanner.fr
In its own wordsLooks like: Software or appSkyscanner
In its own wordsLooks like: Software or appSkyscanner
skyscanner.fr looks like a software product or app, is ranked in the top 10,000 sites and was registered in 2008. It is built with React; we found no traces of an AI site builder.
The page shows little text before its JavaScript runs, so we also read its own script (/sttc/px/captcha-v2/static/js/main.81dbcf5a.js) for traces.
Among the top 10K sites.
A popularity band, not a visit count.
Tranco: #19,246 · Chrome UX Report: Top 10,000 · Majestic Million: #76,938
| Source | Says | As of |
|---|---|---|
| TrancoA research ranking that combines several traffic and link sources, published daily. | #19,246 | list of 27 Oct 2026 |
| Chrome UX ReportRank buckets from Google’s real Chrome traffic, published monthly. | Top 10,000 | Sep 2026 |
| Majestic MillionRanks sites by how many separate networks link to them (links, not visits), published daily. CC BY 3.0 | #76,938 | list of 28 Oct 2026 |
Built with React.
…){}}return null}var Q=Array.isArray,G=a.__CLIENT_INTERNALS_DO_NOT_USE_OR_WARN_USERS_THEY_CANNOT_UPGRADE,K=o.__DOM_INTERNALS_DO_NOT_USE_OR_WARN_…Around it: CDN, DNS, Email, SEO and more.
cf-ray: a53c6b1fbec9c8c6-EWR
x-amz-cf-id: JZ9Dqc6HfMFY1Ovww_CjH5LOAYtkmkGzRjKrgTDp9Jf7Ba6oupfIFw==
skyscanner.fr NS ns-1354.awsdns-41.org.
skyscanner.fr MX 0 skyscanner-fr.mail.protection.outlook.com.
skyscanner.fr TXT google-site-verification=FBqiTdj9d7yXOEVuAM4xjKkVBwUTWEDsJ82f9T3CnFo
skyscanner.fr TXT facebook-domain-verification=pycc5e3br3vakjar0h2p1dnvr2r5qv
Business tools can stay listed after a site stops using them.
We couldn’t read the page; outside records are below.
Signals, not a judgement: missing details are common on small, honest sites.
A second opinion on its security setup: Mozilla’s HTTP Observatory grades the site when you open it. Ten checks before you buy · A signal looks wrong? Report it
Looks like: Software or app.
In its own wordsSkyscanner
Our reading of the page, medium confidence.
Q1319169: Skyscanner, search engine
Wikidata: Owned by Trip.com Group; based in Edinburgh, United Kingdom.
Q1319169: Skyscanner
Each name is quoted from its source. A brand and the company that owns it often go by different names.
Wikidata, the free knowledge base behind Wikipedia, lists this domain as the official website of this item. Volunteers write it; each item shows its sources.
User-agent: Meta-ExternalAgent · Disallow: /
What its robots.txt and robots tags ask of AI crawlers. Each crawler chooses whether to follow it.
Read from what the page says about itself; we haven’t checked whether it’s true.
No AI builder traces found.
We look for what AI site builders such as Lovable, Bolt and v0 leave in a page. Code written with an AI assistant such as Cursor, Claude Code or ChatGPT leaves nothing to find, so we can’t tell whether AI helped.
AI traces: None found
AI site builders leave traces in the sites they make. We look for the traces of 53 of them and show every match with the line it came from, so you can check it yourself.
We test this on 2,275 sites whose makers we know, and publish what we get wrong.
How we test it · Every builder we know · How to tell if a site was built with AI
AI can find it, but not yet read it well: it scores 27 of 100.
It keeps 1 AI training crawler out, and lets AI assistants in: the site’s choice, never scored.
AI readiness
Search engines may list it and crawlers may read it.
To reach Readable:Text without scripts +25Title and description +8
Optional: for sites with an API or a sign-in.
Below the median of the 2,439 most visited sites we read, which is 72.
Text without scripts
Now Little, 10 characters: scripts draw the rest.
Put the page’s text in its HTML, rendered on the server or at build time.
Why it matters: Most AI crawlers don’t run scripts: they read only what the HTML holds.
Skyscanner
The home page of https://www.skyscanner.fr sends only 10 characters of text before its scripts run, so AI crawlers that don’t run JavaScript see an almost empty page. Make the server send the page’s content in its HTML: render it on the server, or prerender each page at build time (static generation), so its headings, text and links are in the HTML before any script runs. Keep the interactive parts working as they do now.
Structured data
Now None found.
Add schema.org structured data, as JSON-LD, to the home page’s HTML.
Why it matters: Structured data tells AI tools and search engines what the site is: a company, a shop, a product.
Add schema.org structured data to the home page of https://www.skyscanner.fr as JSON-LD, in a <script type="application/ld+json"> tag in its HTML: an Organization with its name, url, logo and sameAs links to its official profiles, and a WebSite with its name and url. Add the type that fits what the site offers too, such as Product, Article or LocalBusiness. Use only facts that are true of the site.
Sitemap
Now Listed in robots.txt, but it isn’t a sitemap.
Publish an XML sitemap and list it in robots.txt.
Why it matters: A sitemap lists every page, so crawlers find the ones no link leads to.
Sitemap: https://www.skyscanner.fr/sitemap.xml
Add an XML sitemap at https://www.skyscanner.fr/sitemap.xml that lists the site’s public pages, in the sitemaps.org format, and add the line "Sitemap: https://www.skyscanner.fr/sitemap.xml" to https://www.skyscanner.fr/robots.txt. Generate it from the site’s routes, so new pages are added to it.
Title and descriptionIn part
Now A title, no description.
Give the home page a title and a meta description in its HTML.
Why it matters: A title and a description are the words AI tools and search engines quote first.
<title>Skyscanner</title>
Give the home page of https://www.skyscanner.fr a descriptive <title> and a <meta name="description" content="…"> of about 150 characters that says what the site is and offers (we found: a title, no description). Put both in the HTML the server sends, not set later by scripts.
Files for AI agents
Now None of the 8 we look for.
If agents could use the site, publish what they need where they look.
Why it matters: Agents act for people: they look for these files to know what a site lets them do. Worth it only if agents can use the site.
If AI agents could use https://www.skyscanner.fr for its visitors (to search it, book, buy or sign in), publish what they need at the standard addresses, and only what the site really offers: an MCP server card at /.well-known/mcp/server-card.json if it runs an MCP server, an API catalog at /.well-known/api-catalog (RFC 9727) listing its public APIs, and OAuth protected resource metadata at /.well-known/oauth-protected-resource (RFC 9728) if agents sign in.
llms.txt
Now None found.
Publish a short Markdown summary of the site at /llms.txt.
Why it matters: A short summary for AI models, at an address they can find. A proposal: few AI companies say they read it yet.
Create https://www.skyscanner.fr/llms.txt as llmstxt.org describes it: a Markdown file with an H1 naming the site, a one-paragraph summary in a blockquote, and short sections listing its most useful pages as links, each with a line on what it holds. Serve it as text/plain or text/markdown.
Links for AI tools
Now None in the home page’s headers.
Point AI tools to the site’s files in the home page’s Link header.
Why it matters: A Link header points AI tools to a site’s files from any page, without guessing addresses.
Make the home page of https://www.skyscanner.fr send a Link header (RFC 8288) that points AI tools to the site’s files, for example: Link: </sitemap.xml>; rel="sitemap", </llms.txt>; rel="describedby"; type="text/plain". List only files the site serves.
Markdown copy
Now Not offered: it sends the page’s HTML.
Answer requests for Markdown with a Markdown version of the page.
Why it matters: A Markdown copy gives AI tools the page’s words without the HTML around them.
When a request to https://www.skyscanner.fr asks for Markdown (its Accept header includes text/markdown), answer with a Markdown version of the page’s main content and the header Content-Type: text/markdown. Requests for HTML keep getting HTML; add Vary: Accept so caches keep the two apart.
Sitemap: https://www.skyscanner.fr/sitemap.xml
Skyscanner
<title>Skyscanner</title>
Keeping AI out is the site’s choice, so it never lowers the score.
GPTBotTo answer people and searchLet inOAI-SearchBotChatGPT-UserClaudeBotanthropic-aiClaude-WebTo answer people and searchLet inClaude-SearchBotClaude-UserGoogle-ExtendedTo answer people and searchLet inGoogle-CloudVertexBotPerplexityBotPerplexity-Usermeta-externalagentline 52, kept outFacebookBotlet inTo answer people and searchLet inmeta-externalfetchermeta-webindexerApplebot-ExtendedTo answer people and searchNone namedAmazonbotTo answer people and searchLet inAmzn-SearchBotAmzn-UserCCBotTo answer people and searchNone namedBytespiderTikTokSpiderTo answer people and searchNone namedMistralAI-UserNone of the 27 other AI crawlers we know is kept out.
It gives no Content Signals and no “noai” tag.
Like 29% of the 435 popular sites whose robots.txt we’ve read since 29 Oct 2026, it keeps at least one AI training crawler out. Of the 555 popular sites we’ve checked since 29 Oct 2026, 9% have a page drawn by scripts, 2% send a Markdown copy, 9% have an llms.txt and 3% offer a file for AI agents. How many websites block AI crawlers?
We read the site once, as our named bot: its robots.txt, read as crawlers read it, its home page and the files AI tools ask sites for. What we couldn’t read says so. robots.txt asks and doesn’t enforce: a firewall can treat AI crawlers differently from us.
93 of 100: strong trust signals.
How established and checkable it is; AI traces carry no weight.
Scored on the parts we could check.
A high score isn’t a promise that a business is honest. How the score works.
Registered in 2008; first archived in 2007.
In the web archive: captured in 20 of 20 years · see the first capture
The web archive saw this address on 12 Oct 2007, before its current registration on 15 Jul 2008. It was probably registered again, possibly by a new owner.
Only from what anyone can see: the site’s public pages and public records.
934 checks on 1 Nov 2026, with version 0.6.0 of our checks and version 1.1 of the score.
It looks like a software product or app. See the evidence
Its domain was registered on 15 Jul 2008, 18 years ago. See the evidence
It is built with React; we found 7 technologies in all. See the evidence
It is among the top 10,000 sites, by Tranco, Chrome UX Report and Majestic Million. See the evidence
We found no traces of an AI site builder. That doesn’t prove a person built it: AI coding assistants leave no traces. See the evidence
Wikidata names Skyscanner. See the evidence
Automated findings from the site’s public home page and public records, as of 1 Nov 2026. They describe what we found, not the people or business behind the site, and they may be incomplete or out of date. This is information, not advice. Terms · Report an error
Is this your site? Ask for a correction.