Search Readiness: a beginner's guide
Evaluate search engine optimization readiness
Search readiness: the launch-day SEO checklist nobody warns you about
Search readiness is shorthand for the surprisingly long list of things that have to be true for a brand-new website to actually show up in Google. The frustrating part is that any single item on the checklist can quietly hide your entire site from search engines, even when the rest of the website is perfect. The famous version of this story is the developer who pushes a beautiful new site to production with a leftover `Disallow: /` line in the `robots.txt` file from staging — and accidentally tells Google to ignore the entire domain.
You should care because a website that is invisible to search engines is, for marketing purposes, a website that does not exist. You can spend months on the design, the copy, the brand identity, the photography — and then have all of it earn zero organic traffic because of a 12-character typo in a configuration file you have never opened. The cost of a search-readiness mistake is total. The cost of running through the checklist is twenty minutes.
The five things every search-readiness check looks at:
`robots.txt` allows the right things. This is the file at `yourdomain.com/robots.txt` that tells crawlers what they can and cannot read. The single most common launch-day disaster is a leftover `Disallow: /` from a staging environment, which tells every search engine to ignore the entire site. Google's own documentation on noindex is unambiguous about how dangerous this is.
No accidental `noindex` tags. Many staging environments add a `<meta name="robots" content="noindex">` tag to every page so search engines don't accidentally crawl the in-progress site. If that tag survives the launch, your live pages will never be indexed even though everything else looks fine.
An XML sitemap exists, returns 200, and lists only canonical URLs. Your sitemap is the roadmap you hand to Google. Every URL in it should resolve cleanly (no redirects, no 404s) and should be the canonical version of the page (not a duplicate, not a parameter-tracked variant).
Canonical tags point at the right pages. A `rel="canonical"` link tells Google which version of a page is the "real" one when multiple URLs serve the same content. A misconfigured canonical can quietly tell Google to credit a competitor's URL.
Page-level meta tags are filled in. Every public page should have a unique title tag, a unique meta description, an H1, and (where relevant) Open Graph tags for social sharing. Pages with placeholder titles like "Untitled page" or duplicate descriptions across the entire site are a strong negative signal.
Three questions a search-readiness check answers:
Did anything from staging accidentally make it into production?
Are search engines actually allowed to crawl and index the pages I want them to?
Did I miss any of the basic on-page elements that search engines expect every public page to have?
The cost of skipping this check is the most common avoidable disaster in marketing: launching with confidence, watching the launch land flat for weeks, and only then discovering that Google never actually saw the site. Running through the checklist before pushing the launch button — or asking your AI assistant to run it for you — is one of the cheapest twenty-minute investments anyone in marketing can make.
The Search Readiness endpoint, in plain language
In one sentence: Evaluate search engine optimization readiness
Evaluates how well a domain is prepared for search engines by checking crawlability, indexability, on-page optimization, technical SEO (Search Engine Optimization), content signals, and authority signals.
Don't worry if some of the words above are still unfamiliar — there's a plain-language glossary at the bottom of this page, and most of the terms link to their own beginner guides if you want to learn more.
What is actually happening when you call it
Here's what's actually happening behind the scenes when you call this endpoint:
Performs a multi-factor search readiness assessment: checks robots.txt (robots.txt file) accessibility and sitemap availability (crawlability), verifies meta robots directives and noindex tags (indexability), evaluates title/description/heading optimization (on-page), confirms HTTPS (secure HyperText Transfer Protocol), viewport, and structured data (technical SEO (Search Engine Optimization)), analyzes word count and image coverage (content), and checks CrUX data availability (authority). Each category is scored individually and combined into an overall grade.
If you're using an AI assistant through MCP, you don't need to understand any of the technical details — the assistant calls the tool and translates the result for you.
Why this specific tool matters
Let's skip the marketing fluff and answer the only question that actually matters: why should you, a real human with a real to-do list, care about the Search Readiness tool? Here's the plain-English version, written the way you'd hear it from a friend who happens to do this for a living.
Search readiness goes beyond basic SEO (Search Engine Optimization) — it tells you whether search engines can actually find, crawl, and properly index your content. A site with great content but poor crawlability or noindex tags will never rank.
Picture this in real life. Imagine a web developer. Here's the situation they're walking into: Verify a new website is properly configured for search engine discovery before launch. Without the right tool, that person would be stuck copy-pasting between five browser tabs, reading documentation written for engineers, and crossing their fingers that the answer they cobble together is correct. With the Search Readiness tool, the same person gets a clear answer in seconds — no spreadsheets, no guessing, no waiting for someone on the infrastructure team to free up.
Three questions this tool answers in plain English. If any of these have ever crossed your mind, the Search Readiness tool is built for you:
Are search engines actually able to crawl, understand, and recommend my pages?
What is the single biggest fix I could make today to climb in Google?
How does my site compare against the technical SEO checklist that the top results all pass?
You can either click the tool and get the answer yourself, or ask your AI assistant — connected through MCP (Model Context Protocol) — to ask the question for you and translate the answer into something you can paste into Slack.
Who gets the most out of this. Marketers, content writers, freelancers running client sites, founders trying to grow without paying for ads, and SEO specialists running monthly health checks. If you see yourself in that list, this is one of the EdgeDNS tools you should bookmark today.
What happens if you skip this entirely. Skip it and search engines quietly stop sending you traffic and you don't find out until the next quarterly review. That's why running this check — even once a month — is one of the cheapest forms of insurance you can give your domain.
Available on the developer plan. The technical details: `GET /v1/domain/search-readiness`.
When would I actually use this?
If you're still on the fence about whether the Search Readiness tool belongs in your toolbox, this section is for you. Below you'll meet three real people — a web developer, a technical SEO, and an SEO agency — facing three real situations where this tool turns a stressful afternoon into a five-minute task. Read whichever story sounds closest to your week.
Story 1: Launch Readiness
Imagine you're a web developer. Verify a new website is properly configured for search engine discovery before launch.
Why it matters: Ensure search engines can crawl and index the site from day one.
Story 2: Technical SEO Audit
Imagine you're a technical SEO. Diagnose why a site has low organic visibility by checking all technical SEO (Search Engine Optimization) fundamentals.
Why it matters: Identify technical barriers to search engine indexing.
Story 3: Client Reporting
Imagine you're an SEO agency. Generate search readiness scores for client sites as part of monthly reporting.
Why it matters: Track and demonstrate SEO (Search Engine Optimization) improvement over time.
Common situations across teams. Beyond the three stories above, here are the everyday workplace moments when people across the company reach for the Search Readiness tool — or one of the tools right next to it in this category. If any of these are on your calendar this month, that's your sign:
Before launching a new page, site, or campaign — to catch the dumb mistakes.
During a quarterly SEO health check.
When organic traffic suddenly drops and you need to find out why.
When pitching a new client and you need an audit deck in under an hour.
If you can see yourself in even one of those bullets, the Search Readiness tool will pay for itself the first time you use it.
Still not sure? Here's the easiest test in the world. Open Claude, ChatGPT, Gemini, or any other AI assistant connected to the EdgeDNS MCP server and ask, in your own words: "Is the Search Readiness tool useful for my job?" The assistant will look at the tool, ask you a couple of follow-up questions about what you're trying to accomplish, and give you a straight answer in plain English. No commitment, no signup forms, no jargon.
The easiest way: just ask your AI assistant
If you've connected the EdgeDNS MCP server to Claude, ChatGPT, Gemini, Cursor, or any other AI assistant, you don't need to write any code. Just ask in plain English:
"Use the Search Readiness tool to check example.com and explain anything that looks wrong in plain language."
The AI will figure out which tool to call, fill in the right parameters, run it, and then explain the result back to you. No copy-pasting between tabs. No reading raw JSON. No memorizing endpoint names.
MCP (Model Context Protocol) access is free on every plan, including the free tier. One API key works for both REST and AI — you do not have to choose.
The technical way: call it from code
If you're a developer and want to call the endpoint from a script or your own application, here's the simplest possible example. Replace the placeholder API key with the real one from your dashboard.
# Replace edns_live_YOUR_KEY with your real API key from the dashboard
curl -H "Authorization: Bearer edns_live_YOUR_KEY" \
"https://api.edgedns.dev/v1/domain/search-readiness?domain=example.com"What you need to provide
There's just one piece of information you need to provide. The table below explains exactly what it is and what a real value looks like.
| Field | Type | Required? | What it means | Example |
|---|---|---|---|---|
domain | string | Yes | The domain to evaluate search readiness for | example.com |
What you get back
When you call this tool, you'll get back a JSON object with the fields below. If you're talking to it through an AI assistant, the assistant reads these for you and explains them in plain language — you don't need to memorize them.
| Field | Type | What you'll see in it |
|---|---|---|
domain | string | The evaluated domain |
crawlability | object | Robots.txt, sitemap, canonical check scores |
indexability | object | Meta robots, noindex, X-Robots-Tag analysis |
onPageOptimization | object | Title, description, H1, heading structure scores |
technicalSeo | object | HTTPS (secure HyperText Transfer Protocol), viewport, structured data analysis |
contentSignals | object | Word count, images, alt text (alternative text) coverage |
authoritySignals | object | CrUX data availability and score |
score | number | Overall search readiness score 0-100 |
grade | string | Letter grade A-F |
breakdown | object | Score breakdown by category with individual weights and scores |
recommendations | array | Prioritized improvement actions |
Words you might be wondering about
If any words on this page felt like jargon, here's a plain-language version. Click any linked term to read a full beginner-friendly guide.
HTTPS (secure HyperText Transfer Protocol) — HTTP with encryption — the little padlock in your browser. It means nobody between you and the website can read what you're sending.
SEO (Search Engine Optimization) — Everything you do to help search engines like Google find, understand, and rank your website.
robots.txt (robots.txt file) — A simple text file at the root of a website that tells search engine crawlers which pages they're allowed to look at and which to skip.
Need Programmatic Access?
Automate domain intelligence with 100+ API endpoints and a free MCP server for AI integration.