Indexability Audit Template
Indexability Audit Template
Check status, robots, noindex and canonical on every page you want indexed, then see exactly what to fix first.
Which pages that should be indexed have a technical conflict, which are technically fine but still not indexed, and which were never meant to be indexed.
- Excel workbook (.xlsx), opens in Google Sheets
- PDF field guide, 9 to 11 pages
- Blank and worked CSV templates
- DataForSEO import script
Free, no email required. Version 3.0, updated November 2026.
=IF(I13="","",IF(I13<>"Ready","n.a.",IF(F13=0,"Review exclusion intent",IF(J13=0,"Fix technical conflict",IF(G13=0,"Investigate indexing","Monitor")))))The formula above is the real one from cell K13. Scroll it sideways to read the whole rule.
Connected to the DataForSEO API
This template is designed around one DataForSEO endpoint. Pull the data, convert it with one command, and the workbook does the rest.
DataForSEO On-Page APIA crawl of your site: URLs, status codes, canonicals, inlinks and sitemap membershipon_page/task_post
Save the JSON responseThe full API response, kept as your source of truth.response.json
Run the import scriptOffline. No API calls, no credentials.dataforseo_import.py import --template 11
Paste at A13Dashboard, checks and action list update instantly.Indexability Audit Template.xlsx
Column map for this template:Filled by the APIAudit trail (automatic)You add
What the indexability audit template decides
'Crawled, currently not indexed' and 'Duplicate, Google chose a different canonical' are some of the most common Search Console complaints, and some of the hardest to triage at scale. The cause is often mundane: a non-200 status, a robots block, a stray noindex or a canonical pointing somewhere else.
This indexability audit template checks each URL for those four conditions and compares the result with your intent and Search Console's indexing status. It sorts every row into one of four actions: Fix technical conflict, Investigate indexing, Review exclusion intent, or Monitor.
Who it's for
- SEOs triaging Search Console indexing reports
- Developers verifying templates after a release
- Migration teams checking the new site before and after launch
- Ecommerce teams with faceted or paginated URLs
Where it fits in your workflow
The indexability audit template answers one question. These three templates answer the questions around it:
- XML Sitemap Audit Template: which URLs should be removed from your XML sitemap (or fixed), which eligible URLs are missing from it, and which are fine.
- Hreflang Audit Template: which hreflang relationships pass every check and which need fixing, with the number of failed checks per alternate.
- Redirect Mapping Template: whether each planned redirect actually reaches the approved destination in one permanent hop, on an indexable page whose canonical agrees, with a human sign-off.
What's inside the download
One ZIP with the workbook, an 8-column input template (blank and filled), the PDF field guide and an offline script that converts saved DataForSEO responses into the input CSV. The workbook has five tabs.
How the indexability checker calculation works
Technical readiness = 1 when status is 200, robots allows crawling, noindex is 0 and the canonical equals the URL. The review returns Review exclusion intent when you don't intend to index the page, Fix technical conflict when it isn't technically ready, Investigate indexing when it's ready but not indexed, otherwise Monitor.
The key formula, exactly as it appears in the workbook
=IF(I13="","",IF(I13<>"Ready","n.a.",IF(F13=0,"Review exclusion intent",IF(J13=0,"Fix technical conflict",IF(G13=0,"Investigate indexing","Monitor")))))
| Result column | Plain-English formula | What it tells you |
|---|---|---|
| Observed technical readiness | IF(AND(HTTP status=200,Robots allowed=1,Noindex present=0,Declared canonical=Page URL),1,0) | Observed self-canonical 200 without known crawling/indexing block. |
| Indexability review | IF(Intended indexable=0,"Review exclusion intent",IF(Observed technical readiness=0,"Fix technical conflict",IF(GSC indexed=0,"Investigate indexing","Monitor"))) | Keeps actual GSC indexing separate from crawl readiness. |
The results you will see
Review exclusion intentFix technical conflictInvestigate indexingMonitor
Green meets the checks, red needs fixing first, amber needs a human decision and blue marks an opportunity. Rows with missing or out-of-range inputs are held back in the Input check column until they're fixed, so a half-filled row never sneaks into a total.
How to use the indexability audit template
- List URLs and your intentInclude pages you want indexed and the ones you don't. Mark intended indexable as 1 or 0.
- Crawl for technical signalsRecord status code, whether robots.txt allows crawling, whether the page has noindex, and its canonical URL.
- Add indexing statusUse URL Inspection or the page indexing report to record whether Google has indexed the URL (1/0).
- Work the queue in orderFix technical conflicts first, then investigate indexing on technically ready pages, then confirm exclusions.
The worked example in the Workspace tab. Clear the lime input cells, paste your CSV at A13 (values only) and every result recalculates.
Fill the indexability audit template with DataForSEO
Every template in this library is built to run on DataForSEO data. This one uses DataForSEO On-Page API: a crawl of your site: URLs, status codes, canonicals, inlinks and sitemap membership.
Most of the data columns fill automatically. Add the business inputs listed below, then paste.
- Request the dataSend this request with your DataForSEO API login (HTTP Basic auth).
POST https://api.dataforseo.com/v3/on_page/task_post [ { "target": "yourdomain.com", "max_crawl_pages": 1000 } ]
Post the crawl task, wait for it to finish, then request on_page/pages with {"id": "<task id>", "limit": 1000} and save that response.
- Save the full JSON responseSave the complete response, not just the task ID, next to the template folder.
- Convert it with the included scriptIt runs offline, makes no API calls and never sees your credentials.
python3 Automation/dataforseo_import.py import --template 11 --input response.json --output my-inputs.csv
- Add what the API can't knowRobots allowed, Noindex present, Intended indexable, GSC indexed
- Paste at A13Clear the demo rows, paste the CSV values at Workspace cell A13 and the dashboard updates.
| Fills automatically from DataForSEO | You add |
|---|---|
| Page URL, HTTP status, Declared canonical | Robots allowed, Noindex present, Intended indexable, GSC indexed |
Source reference fills automatically with the task ID, endpoint, location, language, device and snapshot time, so every row is traceable. Before a big pull, estimate the cost with the DataForSEO pricing calculator. The same steps, plus an example request file, are in the download's Automation folder.
Worked example: Northbeam Outdoor
Every template ships filled with data from Northbeam Outdoor, a fictional outdoor-gear retailer that appears across all 40 workbooks, so you can see what useful output looks like before you add your own. This workbook has 16 example rows.
Six example URLs have technical conflicts: a canonical pointing at ?page=1, a stray noindex, a 301, a robots-blocked category, a canonical to a parent folder and a closed store that 404s. One more page is technically clean but not indexed, which is a quality or demand question, not a tag problem.
Result breakdown
| Result | Rows | Share |
|---|---|---|
| Review exclusion intent | 3 | 19% |
| Fix technical conflict | 6 | 38% |
| Investigate indexing | 1 | 6% |
| Monitor | 6 | 38% |
| Input issues | 0 | 0% |
Input fields
Keep the columns in this order when you prepare a CSV. A missing observation stays blank; use 0 only for a measured zero or a verified No. Fields marked DataForSEO can be filled automatically by the included script.
| CSV field | Column | Meaning and rule | Source |
|---|---|---|---|
| url | Page URL | Exact absolute URL. Keep case and query parameters unless a documented normalization rule applies. | DataForSEO: url |
| status_code | HTTP status | Observed crawl status. | DataForSEO: status_code |
| robots_allowed | Robots allowed | 1 only after robots.txt permits crawling for the intended bot. 1 = Yes, 0 = No. | Your records |
| noindex | Noindex present | 1 if a noindex directive is present in rendered meta or HTTP header. 1 = Yes, 0 = No. | Your records |
| canonical_url | Declared canonical | Exact resolved declared canonical URL. Enter MISSING if absent. | DataForSEO: canonical_url |
| intended_indexable | Intended indexable | 1 when the approved strategy intends this URL to be indexed. 1 = Yes, 0 = No. | Your records |
| gsc_indexed | GSC indexed | 1 only when inspected in GSC and reported indexed. Enter 0 for checked and not indexed. 1 = Yes, 0 = No. | Your records |
| source_ref | Source reference | Task ID, export filename and observation scope. Retain the untouched source response separately. Optional. | DataForSEO: source_ref |
Reading the result honestly
A ready crawl response does not prove Google selected this canonical or indexed the page.
Limits. Robots blocking can prevent a crawler from seeing noindex. Blank inspection data stays missing, not an assumed zero.
Indexability checker mistakes to avoid
Tips from practice
- Run this on a template sample after every release.
- Combine with the sitemap audit: URLs in the sitemap should all be technically ready.
- Investigate indexing rows often need better content, internal links or consolidation, not more tags.
Frequently asked questions
What is indexability in SEO?
Whether a page can be crawled and indexed: it returns 200, isn't blocked by robots.txt, has no noindex directive and declares itself (or no other page) as canonical.
Why is my page crawled but not indexed?
Usually because Google doesn't find it valuable or distinct enough, or because it's a near-duplicate of another URL. Technical conflicts should be ruled out first, which this template does.
Does a canonical tag guarantee which URL is indexed?
No. It's a strong hint. Google may choose another canonical if signals conflict.
Should robots.txt be used to remove pages from Google?
No. Use noindex and allow crawling so Google can see it. Robots.txt controls crawling, not indexing.
Use it with these templates
Each template answers one decision. These are the ones that feed into, or follow from, the indexability audit template.
17XML Sitemap Audit TemplateOn-Page API
Reconcile sitemap URLs against status, canonical, robots and noindex to see what to add, remove or fix.
12Hreflang Audit TemplateOn-Page API
Validate every hreflang relationship: alternate status, self-reference, return tags, canonical match and locale codes.
08Redirect Mapping TemplateOn-Page API
Map every old URL to its new home and verify each redirect: one permanent hop, a 200 page, no noindex, matching canonical.
14Crawl Budget Analysis TemplateOn-Page API
Group verified Googlebot requests by URL pattern, measure crawl waste and pick the right fix for each pattern.
18Schema Markup Audit TemplateOn-Page API
Check presence, syntax, required fields, visible-content match and policy for every structured data type you ship.
13Technical SEO Prioritization TemplateOn-Page API
Turn a technical SEO audit into a ranked fix queue by recovered clicks, profit and profit per hour of dev time.
Part of the SEO Migration Toolkit
Get all 6 SEO Migration templates in one ZIP, or the complete set of 40 SEO and GEO templates with the 401-page field handbook.
Further reading on Optimization Theory
Built by Jourdan Rombough, technical SEO and GEO consultant with 15+ years in search. About Jourdan or get an SEO plan.






