Technical SEO Checklist for New Website Builds.

A new website gives your business a clean starting point: faster pages, clearer customer journeys and a structure search engines can understand. This technical SEO checklist for new website builds focuses on the work that should be completed before launch, while the site is still easy to test and adjust.

For a local service business, technical SEO is not separate from lead generation. If a customer can quickly find a service, view it on mobile and submit an enquiry without friction, the foundations are doing their job.

Start with a crawlable site structure

Search engines need a clear path through your website. Plan the main navigation around the pages that matter to customers, such as services, locations, projects, pricing or contact details. Keep important pages within a few clicks of the home page and avoid burying useful content under multiple menu layers.

Every live page should have a single, permanent URL. Choose a consistent format early, including whether URLs use trailing slashes, lowercase words and hyphens between terms. Short descriptive URLs are easier to manage and make sense when shared. For example, `/roof-repairs/` is more useful than a generated string of numbers and parameters.

Set one preferred version of the domain. Your website should resolve consistently over HTTPS and use either the www or non-www version, not both. Redirect all alternatives to the preferred version with permanent redirects. This prevents search engines from treating identical versions as separate pages.

Create and submit an XML sitemap

An XML sitemap is a list of pages you want search engines to consider for indexing. It should include canonical, useful pages only: not search results, tag archives with no purpose, test pages, redirected URLs or duplicate variations.

Generate the sitemap through your CMS or SEO configuration, check that it loads correctly, then submit it through your search engine management tools after launch. A sitemap does not guarantee rankings, but it gives crawlers a clean map of the site.

Check robots.txt and indexing rules

Your robots.txt file controls which areas of the site crawlers may access. Keep it simple. Allow public pages to be crawled and block only sections that genuinely should not be accessed, such as staging areas or certain system paths.

More importantly, check page-level indexing settings. New sites are often built with a site-wide `noindex` setting to keep development pages out of search. Remove that setting before launch. Then intentionally apply `noindex` to pages that should not appear in search, including thank-you pages, internal confirmation screens and low-value utility pages.

Make mobile performance the baseline

Most local website visits begin on a mobile. Test the real customer journey on a phone, not only in a desktop browser. Can someone tap the phone number, find the service they need, read the key information and complete a form without zooming or hunting for controls?

Use responsive layouts that adapt naturally across mobile, tablet and desktop. Buttons need sufficient size and spacing for touch. Forms should request only information needed to start the conversation. A seven-field enquiry form may collect more detail, but it can also reduce completions. For many service businesses, name, contact details, service required and a message are enough.

Page speed is part of this experience. Large images, unnecessary plugins, autoplay media and heavy third-party scripts can all delay the first useful view of a page. Optimise images before upload, serve appropriately sized versions and use modern image formats where practical. Keep the design considered, but do not use a large video background where a well-compressed image will do the job.

Caching and a content delivery network can improve repeat visits and speed delivery for users across Australia and New Zealand. The right setup depends on the platform, hosting arrangement and how often content changes. An ecommerce store, for example, needs more careful caching rules around carts and account pages than a straightforward brochure website.

Use the technical SEO checklist for new website pages

Before content is signed off, review the settings attached to every key page. Titles, descriptions and headings help search engines understand relevance, while structured content helps visitors scan the page.

Each important page needs a unique title tag that describes the service or purpose clearly. Include the business or location only where it adds useful context. A Tauranga electrician may use a title focused on switchboard upgrades in Tauranga, while a national software provider may not need a suburb in every title.

Write a concise meta description for each main page. It does not directly determine rankings, but it can influence whether a person chooses your result. Describe the benefit and page topic accurately rather than repeating keywords.

Use one clear H1 heading per page, followed by logical H2 and H3 headings. Do not select headings merely because they look larger. Heading levels should describe the content hierarchy. This also improves accessibility for people using screen readers.

Canonical tags are another useful safeguard. They tell search engines which version of similar content is the preferred page. Set self-referencing canonicals on normal pages and use a canonical only when there is a genuine duplicate or near-duplicate version. Do not point unrelated service pages to the home page simply to reduce the number of indexed URLs.

Add structured data where it reflects the page

Structured data gives search engines extra context in a machine-readable format. For local organisations, the most practical starting point is organisation or local business information, including business name, logo, phone number, address where applicable, opening hours and service area.

Add relevant structured data for services, products, FAQs, articles or reviews only when that content is visibly present on the page. Markup should support the page, not invent detail for search results. Incorrect or misleading structured data creates maintenance work without helping customers.

Check that business details are consistent across the website. Your contact page, footer, schema and social profiles should use the same primary phone number, business name and address format. If you operate by service area rather than from a customer-facing office, describe that accurately.

Protect users and preserve data

Install a valid SSL certificate and force HTTPS across every page. Check for mixed content, where an HTTPS page loads an image, script or font over an insecure connection. Browsers may block those resources, and customers should not see security warnings when they are ready to make contact.

Set up redirects before retiring an existing website. Map every old page with traffic, backlinks or a clear replacement to the most relevant new URL. Redirecting all old pages to the home page is quick, but often unhelpful for both users and search engines. A former plumbing services page should point to the new plumbing services page, not a generic landing page.

Also prepare a useful 404 page for URLs that do not exist. Keep the normal navigation available, explain that the page cannot be found, and provide a clear route to key services or contact details. This gives visitors somewhere productive to go rather than ending the journey.

Set up measurement before launch day

Install analytics and search performance tracking before the site goes live. Confirm that page views are being recorded and define the actions that count as a conversion: form submissions, phone-number taps, booking requests, quote requests or online purchases.

Test each conversion yourself on mobile and desktop. Submit forms and confirm that notification emails arrive at the correct inbox. Check spam protection does not block legitimate enquiries. If call tracking is used, make sure the displayed number still works and is presented consistently.

For WordPress sites, limit plugins to those with a clear purpose and a maintenance plan. Updates, backups, uptime monitoring and security checks should be scheduled from the start. OctoberCMS and custom web applications need the same discipline, with version updates, error reporting and backup processes documented.

Run a final launch check

Just before launch, crawl the staging site and then the live domain. Look for broken internal links, missing images, redirect chains, accidental noindex tags, duplicate titles and pages returning server errors. Check that the home page, core service pages, contact form, privacy page and any booking or payment flow work as intended.

Once live, monitor the site during the first few weeks. Search engines need time to crawl a new build, and early checks can catch small configuration issues while they are easy to resolve. A well-prepared website is not a set-and-forget asset: regular updates and performance checks keep it fast, useful and ready for the next customer enquiry.