Crawl and indexation

Confirm important pages are crawlable, indexable and internally linked. Review blocked resources, sitemap output and orphan page risks.

Templates and structured data

Check product, collection, blog and page templates for metadata, headings, schema and content duplication.

Performance and apps

Review theme weight, app scripts, image handling and the practical impact of installed SEO apps.

A technical checklist is only useful if it changes what gets fixed

A Shopify technical SEO audit can easily become a long list of warnings that nobody knows how to prioritise.

A crawler says 143 pages have missing meta descriptions. An app adds duplicate schema. A product variant URL has a canonical issue. A collection is five clicks deep. A filtered URL is crawlable. A discontinued product returns 404. A blog post has a slow image. The store owner asks the obvious question:

Which of these actually matters?

That is the question to settle before changing pages.

The purpose of technical SEO is not to make the crawl export look clean. It is to protect the store’s ability to rank, transfer equity, convert visitors and measure what changed.

That means the audit has to start with the pages that matter most: top collections, valuable products, important content, migration URLs, high-traffic landing pages, and templates that affect many URLs at once.

First separate the store by page type

Do not audit a Shopify store as one list of URLs.

A collection page, product page, blog post, Shopify page, filtered URL, vendor URL, tag URL and legacy migrated URL are not trying to do the same job.

Create a sample set before the audit begins:

Page typeSample to includeWhy it matters
HomepageMain entry pageBrand, navigation and crawl paths
Priority collectionsTop revenue/search categoriesCommercial SEO layer
Long-tail collectionsSpecific buying pathsExpansion and architecture
Product pagesBest sellers, weak sellers, variantsProduct evidence and conversion
Blog/guidesOrganic content and buying supportAssisted discovery
Shopify pagesAbout, contact, policy, resourcesTrust and utility
Filtered URLsSize, colour, vendor, price combinationsCrawl/index risk
Legacy URLsOld WooCommerce/WordPress pathsMigration equity
App-generated URLsReviews, feeds, search, filtersTechnical bloat

This one step changes the whole audit. It stops you from treating a harmless issue on a privacy page as if it were equal to a broken canonical on a top collection.

Check whether important pages are reachable

Before analysing page copy, check access.

For each priority page, confirm:

  • the URL returns 200
  • it is not blocked by robots.txt
  • it does not carry accidental noindex
  • it can be found through internal links
  • it is included in the intended sitemap where appropriate
  • it canonicalises to the preferred URL
  • it is not buried unnecessarily deep
  • it does not rely on a fragile app-only path

This is the foundation. If a priority collection cannot be discovered properly, improving its meta description is theatre.

Check sitemap behaviour, but do not trust it blindly

Shopify generates sitemap files automatically, which is helpful. But an automatic sitemap is not the same as a strategy.

The audit should ask:

  • Are important collections included?
  • Are important product pages included?
  • Are old or unwanted pages present?
  • Are noindex pages appearing unexpectedly?
  • Are sitemap URLs canonical and live?
  • Are the sitemap pages internally linked?
  • Has Search Console discovered and processed the sitemap?

A page appearing in a sitemap does not guarantee it is important. A page missing from a sitemap is not always a disaster. The point is consistency: sitemap, canonical, internal links and business priorities should not all be saying different things.

Robots.txt and noindex checks should be cautious

Robots and noindex controls can be useful, but they can also create expensive mistakes.

Do not start a technical SEO audit by changing robots rules. Start by observing what is happening.

Check:

  • whether important pages are blocked
  • whether unwanted URLs are being crawled heavily
  • whether noindex is present on live templates
  • whether app-generated pages create crawl noise
  • whether search, filter, tag or vendor URLs need control
  • whether staging or preview rules accidentally reached production

If a rule change is needed, document the evidence, expected effect and rollback path. A bad robots decision can be harder to diagnose than the original crawl issue.

Canonicals: look for contradictions, not just tags

Most Shopify pages will have canonical tags. The question is whether those canonicals match the store’s actual internal-link and sitemap behaviour.

Look for contradictions:

  • page internally linked heavily but canonicalises elsewhere
  • sitemap lists one URL but links point to another
  • products linked through collection paths when preferred URL is different
  • filtered URLs canonicalising inconsistently
  • migrated URLs redirecting to a page that canonicalises away
  • app-generated markup creating duplicate canonical signals

Canonicals are hints, not magic switches. They work best when the rest of the site agrees with them.

Redirects: separate migration risk from normal housekeeping

A few old 404s on low-value pages may be housekeeping. Broken or irrelevant redirects from a migration can be a revenue problem.

Check:

  • old WooCommerce product URLs
  • old category URLs
  • old WordPress posts and pages
  • old redirect exports
  • campaign URLs
  • backlink targets
  • old internal links still present in content
  • redirect chains and loops
  • homepage fallback redirects
  • redirects to noindex or weak destinations

The fix is not “redirect everything”. The fix is deciding whether each old URL deserves a useful destination.

Use the Shopify redirect mapping guide if this audit finds migration residue.

Collection checks: commercial pages first

Collections are usually the most important SEO templates on a Shopify store.

For priority collections, check:

  • indexability
  • canonical target
  • H1 and page title alignment
  • enough product depth
  • above-grid usefulness
  • below-grid buying guidance where appropriate
  • internal links from navigation, products and guides
  • crawl depth
  • duplicate or near-duplicate sibling collections
  • filter behaviour
  • product availability
  • image and performance issues
  • schema output if relevant

A weak collection is rarely fixed by one metadata edit. It usually needs better structure, better product coverage, clearer intent and stronger internal links.

Product checks: evidence, variants and duplication

Product pages need to help customers and support the wider store architecture.

Check:

  • unique product titles
  • useful product descriptions
  • variant handling
  • product images and alt text
  • specifications and metafields
  • review/question content where available
  • duplicate supplier copy
  • out-of-stock handling
  • discontinued product decisions
  • internal links back to collections
  • structured data accuracy
  • Merchant Center/feed consistency if relevant

A technically indexable product can still be weak if it gives search engines and customers no evidence beyond a SKU and a price.

Filters and faceted navigation need a policy

Filters help shoppers. They can also create crawl bloat.

Check:

  • which filter URLs are crawlable
  • which are internally linked
  • whether parameter combinations create many low-value URLs
  • whether search demand justifies dedicated collections
  • whether filtered pages canonicalise sensibly
  • whether old WooCommerce attribute URLs were redirected correctly
  • whether app-based filters generate extra indexable paths

The decision is not “index filters” or “block filters”. The decision is which demand deserves a proper page.

If a filter represents valuable search demand, build a dedicated collection. If it is only a shopper sorting aid, keep it from becoming an SEO landing page.

Structured data: accuracy beats quantity

Do not audit schema by asking how many schema types the site has. Ask whether the markup accurately describes the visible page.

Check:

  • Product schema on product pages
  • price and availability accuracy
  • review markup only where eligible and visible
  • BreadcrumbList consistency
  • Article or WebPage schema where relevant
  • duplicate schema from apps
  • invalid or contradictory fields
  • Merchant Center consistency

Bad schema often comes from apps overlapping with themes. More schema is not automatically better.

Performance: prioritise commercial templates

Do not make performance checks abstract.

Test the templates that affect revenue:

  • homepage
  • top collection template
  • product template
  • blog/guide template
  • filtered collection state
  • page with review/image/app widgets

Look for:

  • large hero images
  • render-blocking scripts
  • app scripts loaded sitewide
  • review widgets
  • tracking tags
  • image loading behaviour
  • mobile layout shifts
  • product media weight

Performance work should focus on the pages and templates where users actually decide to buy.

App output review

A Shopify app should be judged by what it adds to the storefront.

Check installed apps for:

  • sitewide scripts
  • duplicate metadata controls
  • duplicate schema
  • hidden links
  • performance cost
  • theme modifications
  • unused leftover code
  • overlapping functionality
  • unclear ownership

If nobody can explain why an app is installed and what SEO job it performs, it belongs on the review list.

Reporting and measurement checks

Technical SEO fixes need measurement, especially after migrations and theme changes.

Check:

  • GA4 ecommerce events
  • Search Console property and sitemap coverage
  • landing-page reporting by page type
  • revenue or conversion reporting for organic sessions
  • annotation/change log for theme/app/migration changes
  • rank tracking for priority collections if used
  • crawl comparison before and after fixes

Without this, technical SEO becomes a series of tasks rather than an operating system.

Prioritise issues with severity, not fear

Use four levels:

SeverityMeaningExamples
P1Immediate visibility, revenue or tracking risknoindex on top collection, broken migration redirects, checkout tracking failure
P2Important issue affecting commercial templatesduplicate collection canonicals, slow product template, weak internal links to priority category
P3Useful improvement, not urgentmetadata polish, minor image alt text gaps, low-value broken links
P4Monitor or ignoreharmless warnings, low-value utility pages, legacy junk URLs with no evidence

This keeps the audit useful. Store owners do not need another spreadsheet of warnings. They need to know what to fix first.

Minimum working technical SEO checklist

Use this audit flow:

  1. Define priority page types.
  2. Crawl the site.
  3. Export Search Console and analytics landing pages.
  4. Check status codes and indexability.
  5. Review sitemap, robots and noindex signals.
  6. Check canonicals and preferred URLs.
  7. Review redirects and old migration URLs.
  8. Audit priority collections.
  9. Audit priority product pages.
  10. Check filters and parameter URLs.
  11. Validate structured data.
  12. Review performance on commercial templates.
  13. Review app output.
  14. Confirm tracking and reporting.
  15. Create a severity-ranked fix log.

Where this fits in a Shopify SEO audit

Use this checklist after the Shopify SEO hub and before deeper work on individual templates.

If the audit shows collection weakness, use the collection page SEO guide. If product pages are thin, use the product page SEO guide. If filters create crawl noise, use the faceted navigation guide. If the store recently migrated, connect findings to the redirect mapping guide and crawl/indexing migration checks.

Bottom line

A Shopify technical SEO checklist should not make the store owner feel overwhelmed. It should make the next decision clearer.

The best output is not a perfect crawl score. It is a short, ranked list of fixes that protect the pages most likely to drive revenue, rankings and migration stability.

Quick answer

Run a Shopify technical SEO check by page type: crawlability, indexability, canonicals, sitemap inclusion, robots rules, theme output, schema, internal links, app scripts and page speed.

What you will do

  • Find template-level issues before editing individual pages.
  • Separate Shopify-native settings from theme and app problems.
  • Create a fix list developers and ecommerce operators can actually work through.

What to check first

  • Screaming Frog, Sitebulb or equivalent crawler.
  • Shopify admin for products, collections, redirects, theme and search listings.
  • Google Search Console indexing, sitemap and page reports.
  • Schema validator or Rich Results Test for product and breadcrumb output.
  • PageSpeed/Lighthouse for template-level performance checks.

Work through it in this order

  1. Crawl the store and segment URLs by product, collection, blog, page, filter, vendor, tag and search-result patterns.
  2. Check indexability, canonical tags and sitemap inclusion for each page type.
  3. Inspect the rendered HTML for title, meta description, H1, breadcrumb schema, product schema and duplicate app schema.
  4. Check crawl depth for priority collections and products from the homepage and navigation.
  5. Review robots.txt only after identifying which URL patterns are actually causing crawl waste.
  6. Test app scripts and theme sections on collection, product and content templates.
  7. Prioritise fixes by traffic, revenue, crawl risk and implementation effort.

Real-world notes

  • Shopify technical SEO issues are often template issues. Fixing one product manually does nothing if the product template outputs duplicate schema everywhere.
  • Robots.txt edits are risky when the team has not first separated useful filters from crawl traps.
  • Apps can create technical debt quietly: extra scripts, injected schema, generated pages and changed canonical behaviour.

Final checks

  • URLs segmented by page type.
  • Priority pages crawlable in one to three clicks where possible.
  • Canonicals checked by template.
  • Sitemap URLs sampled.
  • Robots rules reviewed against actual crawl data.
  • Product and breadcrumb schema validated.
  • App scripts reviewed on key templates.
  • Fixes prioritised by commercial impact.

Watch-outs

  • If the store uses a custom theme, theme code may override Shopify-native search listing or schema expectations.
  • If filter URLs are blocked too aggressively, useful collection discovery can be harmed.
  • If products are unpublished by stock rules, technical crawls may show 404s that need merchandising or inventory fixes.
Next action

Start with the crawl/indexing evidence, then move into collection, product, URL or filter guides depending on the failing page type.

Field questions

What is Shopify technical SEO?

Shopify technical SEO covers crawl access, indexation, canonicals, redirects, structured data, URLs, performance, filters, app output and template behaviour.

What should be checked first in Shopify technical SEO?

Start with crawl and indexation blockers on priority pages, then check canonicals, redirects, template-level issues, structured data and app or filter problems.

Can Shopify technical SEO be fully controlled?

Not fully. Shopify controls some URL patterns and platform behaviour, so the goal is to work with the constraints and control what the theme, apps and content can affect.

How do apps affect Shopify technical SEO?

Apps can add scripts, duplicate metadata, change structured data, slow templates or create overlapping features. Audit app output before assuming the theme is the problem.