Netlify SEO
Configures a Netlify-hosted site so search engines can crawl, index, and rank it correctly, avoiding common platform-specific pitfalls.
If you have ever deployed a site on Netlify and wondered why Google indexed the default subdomain instead of your custom domain, you already know the platform is not automatically SEO-friendly.
Key points
- Set a single preferred hostname and 301 redirect all alternate versions to it.
- Add canonical tags to every page that can be reached at multiple URLs.
- Generate and submit an XML sitemap to Google Search Console after each deploy.
- Optimise assets during build: minify CSS and JavaScript, compress images, use pretty URLs.
The default subdomain that stole the rankings
A marketing blog deployed on Netlify with a custom domain example.com but left the default site-name.netlify.app accessible. Google indexed both versions. The blog saw duplicate-content warnings in Search Console and lost ranking for its main keyword. After adding a 301 redirect from the Netlify subdomain to the custom domain and a canonical tag on every page, the duplicate warnings cleared and the keyword returned to position three within six weeks, illustrating how long it takes for Google to update SEO after a change.
Three ways it goes wrong
- Duplicate indexable URLs Leaving the default.netlify.app subdomain live alongside your custom domain creates two indexable versions of every page, splitting link equity, wasting crawl budget, and confusing crawlers, similar to iframe seo issues where embedded content may not be indexed.
- Missing canonical tags Without a canonical tag, Google must guess which URL variant is the original. It often picks the wrong one, especially when pages are reachable via www and non-www.
- Redirect chains from builds Each deploy can introduce new redirect rules. A chain of three or more 301s wastes crawl budget and slows discovery of your actual content.
Three checks before every deploy
- Verify redirect behaviour After a deploy, test that the default subdomain, www, and any trailing-slash variants all redirect cleanly to your canonical URL with a single 301.
- Confirm sitemap submission Ensure your sitemap is regenerated after each build and resubmitted to Google Search Console. A stale sitemap can leave new pages undiscovered for weeks.
- Multiple location SEO If your site serves multiple locations, ensure each location page has a unique canonical and is not blocked by redirects. Avoid duplicate content across branches.
Common questions
Does Netlify affect crawl budget?
Yes. Redirect chains and duplicate URLs waste crawl budget. A clean site structure on Netlify helps Google spend its budget on your real pages.
How long does it take for SEO to update after a Netlify change?
How long does it take for SEO to update? Redirect and canonical fixes can reflect in Search Console within days, but ranking changes usually take three to six months depending on crawl frequency.
Sources
- Google Search Central Covers canonical tags, redirects, sitemaps, and crawl budget.
- Netlify Docs Platform-specific settings for redirects, deploy config, and asset optimisation.