Key takeaways
- A technical SEO checklist confirms that search engines can crawl, render and index the pages you want ranked, and that they pick the right version of each page.
- Core Web Vitals are judged at the 75th percentile of real users: LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1 count as good.
- Most company sites lose more to indexing mistakes (stray noindex, wrong canonicals, orphan pages) than to speed, so check those first.
- Structured data, internal links and hreflang help search engines and AI assistants understand what each page is and who it is for.
A technical SEO checklist verifies that search engines can crawl your site, render each page, index the right version of it and understand what it is about. For most company websites the priority order is indexing first (robots.txt, noindex, canonicals, sitemaps), then page experience (Core Web Vitals: LCP under 2.5s, INP under 200ms, CLS under 0.1), then meaning (schema, internal links, hreflang). Fix in that order and every content investment afterwards works harder.
We use the same checklist on every website we build or take over. Below is the table version, then the context behind the items that cause the most damage.
What should a technical SEO checklist cover?
The table is ordered by impact. Work top to bottom and do not move on until each line passes.
| Area | What to check | Pass condition | Where to check |
|---|---|---|---|
| Crawl | robots.txt, server errors, blocked resources | Important pages and their CSS/JS are crawlable; no 5xx on key templates | robots.txt, Search Console crawl stats, a crawler |
| Index | noindex tags, Page indexing report | Every page you want ranked is indexed; thin, duplicate and utility pages are not | Search Console Page indexing, URL Inspection |
| Canonical | rel=canonical on each template | Self-referencing on unique pages; points to the main version on duplicates; Google's chosen canonical matches yours | URL Inspection, crawler |
| Sitemap | XML sitemap content and freshness | Lists only indexable, canonical, 200-status URLs with accurate lastmod; submitted in Search Console | Search Console Sitemaps |
| Redirects and status | 301s, chains, 404s, soft 404s | One-hop 301s; no internal links to redirects or 404s | Crawler, Search Console |
| Core Web Vitals | LCP, INP, CLS on mobile and desktop | LCP < 2.5s, INP < 200ms, CLS < 0.1 at the 75th percentile of real users | Search Console Core Web Vitals, PageSpeed Insights |
| Mobile rendering | Content parity, tap targets, viewport | Mobile page shows the same content and links as desktop | URL Inspection rendered HTML |
| Schema | Structured data type and validity | Organization, LocalBusiness, Article, BreadcrumbList or Product where relevant; no errors | Rich Results Test, Schema validator |
| Internal links | Click depth, orphan pages, anchors | Key pages within 3 clicks of home; no orphans; descriptive anchors | Crawler |
| Hreflang | Language and region annotations | Reciprocal, self-referencing, valid codes, x-default set | Crawler, Search Console |
Crawl and index: where most traffic is lost
On company websites we rarely find that speed is the main problem. We find pages that cannot be indexed. A typical story: a Jakarta company relaunches its site before a product launch, the new design looks great, and three weeks later organic leads have dried up because half the service pages are not in Google.
“If Google cannot index the page, nothing else on it matters.”
The usual causes:
- A staging noindex that went live. A developer adds noindex to the test site, the setting ships to production, and the site slowly disappears.
- robots.txt blocking the wrong folder, sometimes including the JavaScript files Google needs to render the page.
- Parameter and filter URLs creating thousands of near-duplicate pages that dilute crawling.
- Orphan pages that exist in the sitemap but have no internal links, so Google treats them as unimportant.
Remember that robots.txt controls crawling, not indexing. To keep a page out of results, let Google crawl it and use noindex.
Open the Page indexing report in Search Console and read every reason under "Not indexed". "Crawled, currently not indexed" usually means Google saw the page and did not think it was worth keeping, which is a content or duplication signal, not a technical bug.
Canonicals and sitemaps: telling Google which version counts
A canonical tag is a hint, not a command. Google will ignore it if other signals disagree, for example if your internal links, sitemap and redirects all point to a different URL. Keep the signals consistent:
- Every unique page has a self-referencing canonical.
- Internal links point to the canonical URL, not to a redirected or parameter version.
- The XML sitemap lists only canonical, indexable URLs that return a 200 status.
Google ignores the priority and changefreq fields in sitemaps, but it does use lastmod when it is accurate. Only update lastmod when the content meaningfully changes.
Core Web Vitals thresholds and what usually breaks them
Google measures Core Web Vitals from real Chrome users and judges a page "good" when 75% of visits meet the threshold.
| Metric | Measures | Good | Common cause on company sites |
|---|---|---|---|
| LCP (Largest Contentful Paint) | Loading of the main content | under 2.5s | Uncompressed hero images, slow hosting, render-blocking fonts and scripts |
| INP (Interaction to Next Paint) | Response to clicks and taps | under 200ms | Heavy third-party scripts: chat widgets, tag bloat, sliders |
| CLS (Cumulative Layout Shift) | Visual stability | under 0.1 | Images without dimensions, late-loading banners and cookie bars |
INP replaced First Input Delay as a Core Web Vital in 2024, so older audits that only report FID are out of date. On the sites we take over, the fastest wins are usually serving hero images in WebP or AVIF at the right size, removing tags nobody uses, and reserving space for anything that loads late.
Schema, internal links and hreflang: helping machines understand you
Once pages are indexed and fast, help search engines and AI assistants read them correctly.
Structured data. Mark up who you are (Organization or LocalBusiness), what the page is (Article, Product, Service) and where it sits (BreadcrumbList). FAQ rich results are now shown only for a narrow set of authoritative sites, so do not add FAQ schema expecting extra listings. The real value of schema today is clarity: it gives Google and AI systems unambiguous facts to quote. We cover this further in how to get your brand cited in AI search.
Internal links. Your most valuable service pages should be reachable within three clicks from the homepage and linked from related articles with descriptive anchors. Internal linking is one of the few signals entirely in your hands.
Hreflang. For EN and ID versions of the same page, each version must reference itself and the other, use valid codes (en, id, or en-SG style region codes), and include an x-default. One-way hreflang is ignored. Our guide to bilingual website SEO and hreflang goes through the setup step by step.
How we run technical SEO at FOXA
We start every SEO engagement with a crawl, a Search Console review and a live test of the conversion events, because a site that ranks but cannot measure leads is only half fixed. The output is a ranked fix list with developer-ready tickets, not a generic score. See our SEO and website services for the full scope.
For Bali Bird Park, the program combined technical cleanup, content and social work, and delivered +56% organic website traffic. Along the way we found and fixed a mis-firing checkout event, so purchases were once again counted correctly. That is the point of putting tracking checks inside an SEO audit: you need to see whether the extra traffic actually converts. Our tracking audit guide explains that side of the work.
Where to start this week
Open Search Console, read the Page indexing report and check your three most important pages with URL Inspection. Then run the table above against your homepage, one service page and one article.
If the report lists more "Not indexed" reasons than you expected, book a call. We will look at the Search Console data with you and say which fixes we would do first.
Questions we get asked
What is included in a technical SEO checklist?
A technical SEO checklist covers everything that decides whether search engines can find, render and index your pages correctly. That means robots.txt and crawlability, indexing directives, canonical tags, XML sitemaps, Core Web Vitals and mobile rendering, structured data, internal linking, redirects and status codes, and hreflang for multilingual sites. It does not cover keyword research or content writing.
How often should a company website get a technical SEO audit?
Run a full audit once or twice a year, and a short check after every site release, migration, CMS change or redesign, because that is when most technical problems appear. Between audits, review the Page indexing and Core Web Vitals reports in Google Search Console every month so you catch new errors before they cost traffic.
Does Core Web Vitals affect Google rankings?
Core Web Vitals are part of Google's page experience signals, so they do play a role, but relevance and content quality matter far more. A fast page with weak content will not outrank a slower page that answers the query better. Treat good Core Web Vitals as a baseline that protects conversions and removes a disadvantage, not as a ranking shortcut.
What is the difference between noindex and blocking in robots.txt?
Robots.txt tells crawlers not to fetch a URL, while a noindex tag tells search engines not to show a page they have fetched. If you block a page in robots.txt, Google cannot see its noindex tag, so the URL can still appear in results if other pages link to it. To remove a page from the index, allow crawling and use noindex.
About FOXA DigitalFOXA Digital is a performance marketing agency in Jakarta, Indonesia. Since 2018 we have run paid media, tracking, SEO and content for apps, consumer brands, hospitality and attractions, judged on CAC, ROAS and leads.
Want us to look at your numbers?
30 minutes. No deck. You leave with three things to fix this week.



