Technical SEO is the work that makes a website accessible to crawlers, understandable to search engines and usable for visitors. It does not replace useful content or a strong product offering. It removes technical obstacles that can prevent important pages from being discovered, crawled, rendered, indexed or presented correctly.
This checklist is designed for modern websites, including Shopify stores. Work through it in order: first confirm that search engines can access the right URLs, then check indexability and canonical signals, then review performance, rendering, structured data and monitoring.
1. Crawlability: can Google fetch the important pages?
- Open the live website as an anonymous visitor and confirm that important pages return a successful HTTP response.
- Check the site's robots.txt file and make sure it does not block important product, collection, article, CSS or JavaScript resources.
- Use the Search Console URL Inspection tool on representative product, collection and blog URLs to see whether Google can crawl and render them.
- Review server logs or crawl data for repeated 5xx errors, long response times, redirect chains and unnecessary URL variations.
- Make sure important pages are discoverable through ordinary HTML links, not only through buttons or scripts that crawlers may not follow.
Important distinction: robots.txt is primarily a crawl-control mechanism. It is not a reliable substitute for a noindex directive. A blocked URL can still be known to Google from links or other signals, even if its content cannot be fetched.
2. Indexability: should the page appear in search?
- Check that important pages do not accidentally carry a noindex meta tag or X-Robots-Tag header.
- Confirm that canonical tags point to the preferred URL.
- Look for duplicate URLs created by tracking parameters, product variants, filters, sorting and alternate paths.
- Do not canonicalise a useful, unique page to a different page merely to reduce the number of URLs.
- Review Search Console's Page Indexing report for excluded, crawled-not-indexed and discovered-not-indexed URLs.
- For each high-value page, compare the user-declared canonical with Google's selected canonical in URL Inspection.
3. XML sitemap checklist
- Confirm that the XML sitemap loads and returns valid XML.
- Include canonical, indexable URLs that you actually want in search results.
- Exclude redirected, noindex, duplicate and error URLs from the preferred sitemap set.
- Use absolute, fully qualified URLs and correct canonical destinations.
- Submit the sitemap in Google Search Console and monitor its processing status.
- Recheck the sitemap after changing URL structures, migrating platforms or removing large groups of pages.
Submitting a sitemap is a discovery hint, not an indexing guarantee. Google decides whether and when to crawl and index the URLs.
4. Canonicals, redirects and duplicate content
| Issue | What to check | Practical action |
|---|---|---|
| Duplicate product or article URLs | Are multiple URLs showing substantially the same page? | Choose the preferred URL and use consistent canonical signals |
| Changed handle or slug | Does the old URL still receive traffic or backlinks? | Use a relevant permanent 301 redirect and update internal links |
| Redirect chain | Does a URL pass through several redirects? | Point links and redirects directly to the final destination |
| Broken internal link | Does a menu, article or product page link to a 404? | Fix the link or redirect it to the closest relevant live page |
| Parameter URLs | Are filters, sorting or tracking parameters generating duplicates? | Control crawl paths and canonical signals without hiding useful pages |
For permanent moves, Google recommends server-side permanent redirects where possible. Do not change a live Shopify handle merely to insert another keyword; the risk to existing links can outweigh a small wording benefit.
5. Core Web Vitals and page experience
Use field data rather than relying only on a single Lighthouse test. Google's current Core Web Vitals guidance defines these “good” thresholds at the 75th percentile of page loads:
| Metric | Good threshold | What it measures |
|---|---|---|
| LCP | 2.5 seconds or less | Loading performance of the main content |
| INP | 200 milliseconds or less | Responsiveness to user interactions |
| CLS | 0.1 or less | Unexpected layout movement |
Check mobile and desktop separately. On a Shopify store, common investigation areas include oversized hero images, app scripts, multiple review widgets, unused theme code, render-blocking assets, heavy fonts, chat pop-ups and layout shifts caused by images or banners without reserved dimensions.
6. JavaScript rendering
- Make sure the main page content and product information are present in the rendered HTML that search engines can process.
- Test pages with the URL Inspection live test or a browser rendering tool.
- Do not hide essential product descriptions, navigation links or article content behind interactions that require a visitor-only event.
- Check whether apps inject important content late or create errors in the browser console.
- Where practical, keep critical content server-rendered or available in the initial HTML.
Google processes JavaScript pages through crawling, rendering and indexing stages. Rendering can introduce delays and other crawlers may not execute JavaScript in the same way, so making important content accessible without unnecessary client-side dependency is a safer approach.
7. Internal linking and site architecture
- Every important product, collection and article should have at least one relevant internal link from another crawlable page.
- Use descriptive anchor text that tells visitors what they will find after clicking.
- Link from broad guides to specific product pages where the product genuinely supports the topic.
- Link between related articles in the same cluster, but avoid repeating the same exact-match anchor on every page.
- Keep navigation and breadcrumb paths understandable.
- Remove orphan pages or give them a clear place in the site's information architecture.
8. Structured data and rich-result eligibility
Use structured data only when it accurately describes visible page content. For eligible pages, common types include Product, Article, BreadcrumbList, Organization and other supported types relevant to the page. JSON-LD is Google's recommended format for most implementations.
- Validate markup with the Rich Results Test and inspect relevant Search Console enhancement reports.
- Keep product price, availability, rating and review data consistent with what users can see.
- Do not add fabricated reviews, hidden FAQ text, misleading claims or schema for content that is not on the page.
- Re-test structured data after theme changes, app installations and product-template edits.
Correct structured data makes a page eligible for certain rich-result appearances; it does not guarantee that Google will display them or improve the page's ordinary ranking.
9. Image and media optimisation
- Use descriptive filenames and useful alt text for meaningful images.
- Compress large images and use modern formats where supported.
- Reserve image dimensions to reduce layout shifts.
- Lazy-load below-the-fold images, but avoid delaying the main above-the-fold image unnecessarily.
- Check that image URLs are crawlable and not blocked by robots rules.
10. Search Console monitoring checklist
- Review Page Indexing and URL Inspection for important URLs.
- Monitor sitemap processing and submitted-versus-indexed patterns.
- Track query and page performance separately by clicks, impressions, CTR and average position.
- Compare mobile and desktop performance.
- Check Core Web Vitals reports for groups of affected URLs.
- Inspect manual actions and security issues.
- After a significant fix, request recrawling for a small set of priority URLs and monitor the result; do not repeatedly submit the same URL expecting faster indexing.
Shopify-specific technical SEO checks
- Check that the automatically generated
/sitemap.xmlincludes the canonical product, collection, page and blog URLs you want indexed. - Review product and collection canonical tags, especially where products appear in multiple collection paths.
- Check faceted navigation, tag pages and query parameters for unnecessary crawl expansion.
- When changing a product or article handle, create and test the relevant redirect.
- Audit apps that inject scripts, structured data, pop-ups or duplicate metadata.
- Check that the theme outputs unique titles, meta descriptions, canonical tags and useful heading structure.
- Test representative pages on mobile, including collection filters, product variants and cart interactions.
Recommended technical SEO audit order
| Priority | Task | Why it comes here |
|---|---|---|
| 1 | Fix blocked, erroring or noindex pages that should be indexed | Search engines cannot use pages they cannot access or index |
| 2 | Correct canonicals, redirects and duplicate URL signals | Consolidates signals and avoids wasting crawl effort |
| 3 | Repair sitemap and internal-link discovery | Helps important URLs be found |
| 4 | Improve Core Web Vitals and mobile usability | Improves real user experience and responsiveness |
| 5 | Validate rendering, metadata and structured data | Improves how pages are interpreted and represented |
| 6 | Monitor Search Console and repeat the audit | Confirms whether fixes worked and catches regressions |
Official technical SEO references
- Google Search Central — Crawling and Indexing
- Build and Submit a Sitemap
- JavaScript SEO Basics
- Redirects and Google Search
- General Structured Data Guidelines
- Core Web Vitals
Learn more about technical SEO
LyWire's Technical SEO for Modern Websites Handbook is a paid reference guide for website owners and marketers. You can browse the IT Skill collection for related digital resources. Review the product description to confirm its scope before purchase.
For an adjacent topic, see LyWire's existing article on voice search versus traditional search.
Information checked: 15 November 2026. Search documentation, supported rich results and performance metrics can change. Use current Google Search Central documentation and Search Console reports when auditing a live site.