Do I need SEO before my website launches?

Yes — certain SEO elements need to be in place on launch day, not added later. Google starts crawling new sites quickly, and if robots.txt is blocking indexing, your canonical URLs are wrong, or your sitemap is missing, you will have indexed errors that take time to correct even after you fix the underlying files. The pre-launch window is the lowest-cost time to get these right because there is no existing indexed state to repair. Adding SEO after launch is possible but costs more time than doing it before.

How long does it take for a new website to show up in Google?

Most new sites see their first pages indexed within one to four weeks of launch if they are verified in Google Search Console and have a sitemap submitted. Ranking for competitive terms takes longer — often three to six months of consistent content and backlinks. The pre-launch checklist does not accelerate ranking directly, but it removes the delays caused by technical mistakes (blocked pages, missing sitemaps, incorrect canonicals) that can push indexing out months past launch.

What is a sitemap and why does it matter at launch?

A sitemap is a file (usually sitemap.xml) that lists every URL you want Google to index, with the date last modified. It tells Google's crawler which pages exist and which are the priority pages — without it, Google discovers your content by following links from other pages, which is slower and less reliable for a brand-new site with no external links pointing to it. Submitting your sitemap through Google Search Console at launch is the fastest way to signal that your site is ready to be indexed.

Does page speed affect SEO?

Yes, but it is a secondary factor compared to content relevance and link authority. Google's Core Web Vitals (LCP, CLS, INP) are ranking signals — a site with a 7-second load time on mobile will be penalized relative to a comparable site loading in 2 seconds. For most service businesses, the largest speed problem is unoptimized images: a 1.5MB hero image that could be a 60KB WebP. Fixing image compression alone often moves LCP from failing to passing without touching code. The pre-launch window is the right time to baseline your page speed because fixing images before indexing avoids a known-bad crawl.

What is NAP consistency and why does it matter for local SEO?

NAP stands for Name, Address, Phone — the three fields that appear on your website, your Google Business Profile, and directory listings like Yelp and the BBB. Google uses NAP matching to verify that a business is real and to confirm that the website and the Business Profile are the same entity. Inconsistencies — an old address on the website, a different phone number on Yelp, or a slightly different business name on directories — weaken your local SEO signals. The fix is to make your website NAP exactly match your Google Business Profile, then update any directory listings that use different information.

← Journal Checklist Jun 27, 2026

Pre-launch website SEO checklist for small service businesses.

12 items to verify before your site goes live — the ones most designers skip and most business owners never find until they wonder why nothing is showing up in Google.

Most SEO problems on new websites are not content problems. They are setup problems — wrong settings, missing files, or blocked pages that were never tested before the site went live. By the time you notice something is wrong, the bad state has already been crawled and indexed. Correcting it takes longer than getting it right before launch.

This checklist covers the 12 items with the highest chance of causing an indexing or ranking problem on a new service business site. None require technical expertise to verify — each check has a plain-English description of what to look for and what to do if it is wrong.

The checklist

1. Google Search Console is set up and verified

Google Search Console is the free tool that shows you how Google sees your site — which pages are indexed, which have errors, and how your content is performing in search. Without it, you are flying blind. Verify your site in Search Console before launch using the HTML file method or the DNS TXT record method (not the Google Analytics snippet method — it is slower to propagate). Once verified, submit your sitemap and confirm there are no immediate crawl errors.

If not done: Set up Search Console now. It is free and takes under 30 minutes. See the separate guide: How to set up Google Search Console for your small business website.

2. Sitemap.xml exists and is submitted

Your site needs a sitemap.xml file at yourdomain.com/sitemap.xml that lists every page you want Google to index. After verifying in Search Console, submit the sitemap URL. Without a sitemap, Google discovers pages only through links — on a brand-new site with no external links, that means slow, incomplete indexing.

Check: Visit yourdomain.com/sitemap.xml in a browser. If you see an XML file listing your URLs, the sitemap exists. If you see a 404 or a blank page, it does not.

3. Robots.txt is not blocking Google

Robots.txt is a file at yourdomain.com/robots.txt that tells crawlers which pages they can and cannot access. The most common pre-launch mistake is leaving robots.txt set to Disallow: / — a development-mode setting that blocks all crawling — and forgetting to change it before launch. If your site is not showing up in Google weeks after launch, this is the first place to check.

Check: Visit yourdomain.com/robots.txt. If you see Disallow: / with no qualifier, your entire site is blocked. The production setting should be Allow: / or simply not include a Disallow directive for the root path.

4. Every page has a unique title tag and meta description

Title tags are the blue links in Google search results. Meta descriptions are the snippet of text below them. Both affect click-through rate and tell Google what the page is about. Every page should have a unique title (50–60 characters) and a unique meta description (120–160 characters). The most common problem is pages that share the same title across the site, or that use the site name only with no page-specific content.

Check: View source on your homepage and services page and search for <title> and <meta name="description". Both should be present and different between pages.

5. Canonical URLs are set correctly

A canonical URL tells Google which version of a page is the "official" one when the same content is accessible at multiple URLs (for example, yourdomain.com/services and yourdomain.com/services/ with a trailing slash). Without canonical tags, Google may split your authority between duplicate versions. Every page should have a <link rel="canonical"> tag pointing to its own URL, consistently using or not using the trailing slash.

Check: View source on any page and search for rel="canonical". The href should be the exact URL you want Google to use as the primary version.

6. HTTPS is working and there is no mixed content

Your site should be served over HTTPS (you will see the padlock icon in the browser). HTTP sites are flagged by Chrome as "not secure" and receive a small ranking penalty. Mixed content — a page loaded over HTTPS that also loads images or scripts over HTTP — generates browser warnings. Both are easy to fix before launch and increasingly rare with modern hosting, but worth verifying.

Check: Visit your site and confirm the padlock is showing. Open browser DevTools (F12), click the Console tab, and look for "Mixed Content" warnings.

7. Open Graph and social sharing tags are in place

Open Graph tags control how your pages appear when shared on Facebook, LinkedIn, or in iMessage links. Without them, shared links use whatever content the scraper finds first — often the wrong image or a truncated snippet. Every page should have at minimum: og:title, og:description, og:image (at least 1200×630px), and og:url. The homepage and services page are the highest priority.

Check: Paste your URL into opengraph.xyz or the LinkedIn Post Inspector. Both show you exactly what will appear when the URL is shared.

8. Page speed baseline passes on mobile

Run your homepage through Google PageSpeed Insights (free, at pagespeed.web.dev) on mobile. A passing LCP (Largest Contentful Paint) is under 2.5 seconds. The most common failure is an unoptimized hero image — a 1–2MB PNG or JPEG that should be a 50–100KB WebP. Fix image compression before launch; it is harder to fix after content is indexed and users are comparing your site to competitors.

Check: Run the homepage on PageSpeed Insights. If LCP is over 2.5 seconds, identify the largest image on the page and convert it to WebP at reduced size. Most image editing tools and free online converters handle this in under five minutes.

9. The site renders correctly on mobile

Google indexes the mobile version of your site first (mobile-first indexing). If the mobile experience has broken layouts, overflowing text, or buttons that are too small to tap, both your ranking and your conversion rate will suffer. Test on an actual phone, not just a browser resize — browsers and real devices behave differently, especially on older iOS versions.

Check: Open the site on your phone. Tap every button. Scroll every page. Confirm text is legible at 375px wide and no element overflows horizontally.

10. Your business name, address, and phone match your Google Business Profile

NAP consistency (Name, Address, Phone) matters for local SEO. If your website shows a different phone number than your Google Business Profile, or an old address, Google's local algorithm treats them as weaker local signals. Make your website NAP exactly match your Business Profile before you launch — then update any directories that have old information.

Check: Open your Google Business Profile and compare the name, address, and phone number to what appears in the footer or contact section of your website. They should be character-for-character identical in the information they convey, even if formatting differs slightly.

11. A 404 page exists and is useful

A 404 page appears when someone visits a URL that does not exist — a mistyped link, a moved page, or a dead link from another site. A missing or blank 404 page frustrates visitors and gives them no path back to your site. A useful 404 page acknowledges the error, links back to the homepage and services, and may include a brief message. Most platforms generate a basic 404 automatically; verify yours is returning a 404 status code (not a 200) by visiting a made-up URL on your site.

Check: Visit yourdomain.com/doesnotexist. You should see a branded error page, not a server error or a blank page.

12. Internal links connect your most important pages

Internal links — links from one page on your site to another — tell Google which pages are important and how your content is organized. A site where every page exists in isolation (no links between services, no blog posts linking to the services page) is harder for Google to understand. Before launch, confirm that your homepage links to your services page, your services page links to the contact or brief page, and any blog posts link back to the relevant service pages.

Check: Start at your homepage and click your way to every key page using only links within the site. If you cannot navigate to a page without typing the URL, that page is not well-linked.

What to do after launch

After your site goes live:

Return to Google Search Console and confirm the sitemap was processed without errors.
Use the URL Inspection tool in Search Console to request indexing for your homepage and most important service page.
Set up a Google Business Profile if you have not already, and connect your website URL to it.
Run a full site crawl (Screaming Frog has a free tier for up to 500 URLs) to catch any broken internal links or missing meta tags.

This checklist gets you to a clean baseline. It does not replace ongoing SEO work — content, backlinks, and consistent updates are what build ranking over time. But a clean baseline means every effort you put in after launch starts from a known-good state instead of a hole you are trying to climb out of.

Want an expert to run this checklist on your site?

A site audit covers every item on this list plus a full review of your existing content, conversion rate, and technical setup — with specific fixes, not a generic report. Or if you are building a new site, send a brief and we will wire all of this in from the start.

See the site audit → Send a brief →

Common questions

Do I need SEO before my website launches?: Yes — certain SEO elements need to be in place on launch day, not added later. Google starts crawling new sites quickly, and if robots.txt is blocking indexing, your canonical URLs are wrong, or your sitemap is missing, you will have indexed errors that take time to correct even after you fix the underlying files. The pre-launch window is the lowest-cost time to get these right because there is no existing indexed state to repair. Adding SEO after launch is possible but costs more time than doing it before.
How long does it take for a new website to show up in Google?: Most new sites see their first pages indexed within one to four weeks of launch if they are verified in Google Search Console and have a sitemap submitted. Ranking for competitive terms takes longer — often three to six months of consistent content and backlinks. The pre-launch checklist does not accelerate ranking directly, but it removes the delays caused by technical mistakes (blocked pages, missing sitemaps, incorrect canonicals) that can push indexing out months past launch.
What is a sitemap and why does it matter at launch?: A sitemap is a file (usually sitemap.xml) that lists every URL you want Google to index, with the date last modified. It tells Google's crawler which pages exist and which are the priority pages — without it, Google discovers your content by following links from other pages, which is slower and less reliable for a brand-new site with no external links pointing to it. Submitting your sitemap through Google Search Console at launch is the fastest way to signal that your site is ready to be indexed.
Does page speed affect SEO?: Yes, but it is a secondary factor compared to content relevance and link authority. Google's Core Web Vitals (LCP, CLS, INP) are ranking signals — a site with a 7-second load time on mobile will be penalized relative to a comparable site loading in 2 seconds. For most service businesses, the largest speed problem is unoptimized images: a 1.5MB hero image that could be a 60KB WebP. Fixing image compression alone often moves LCP from failing to passing without touching code. The pre-launch window is the right time to baseline your page speed because fixing images before indexing avoids a known-bad crawl.
What is NAP consistency and why does it matter for local SEO?: NAP stands for Name, Address, Phone — the three fields that appear on your website, your Google Business Profile, and directory listings like Yelp and the BBB. Google uses NAP matching to verify that a business is real and to confirm that the website and the Business Profile are the same entity. Inconsistencies — an old address on the website, a different phone number on Yelp, or a slightly different business name on directories — weaken your local SEO signals. The fix is to make your website NAP exactly match your Google Business Profile, then update any directory listings that use different information.