Website Launch Checklist for SME NZ
Canonical URLs, redirects, forms, analytics, backups, and post-launch checks.
Reading path
Websites and search basics
A practical order to work through website launches, canonical URLs, sitemaps, analytics, and SEO basics. It is written for SMEs and personal projects that need clean, checkable signals.
Start here
Make the site technically sane before chasing rankings
A lot of SEO problems are actually website launch problems: broken redirects, duplicate canonical URLs, missing analytics, no sitemap coverage, or a site that was never checked after going live.
SME SEO Consultant NZ Guide
Service pages, local proof, content that answers real questions, and measurement that matches intent.
Public Source Archive SEO Checklist
A proof-driven checklist for connecting repos, Pages sites, case studies, screenshots, and profiles.
Technical SEO Audit Checklist NZ
A technical sanity check for canonicals, redirects, indexing signals, sitemaps, structured data, and internal links.
Why Your Competitor Has More Google Results Than You
A plain-English look at service pages, location pages, topic hubs, and why one domain can earn several useful results.
Search surface
Create distinct pages instead of repeating the same page
Multiple results from one domain usually come from a cluster of pages that solve different jobs: a homepage, a service page, a location page, a guide, a project note, and a supporting topic hub. The pages need to be genuinely different, internally linked, and useful on their own.
Homepage
Use the homepage as the identity and navigation anchor. It should explain who the site represents, the main areas of work, and the most important pages to visit next.
Service pages
Give each service page a clear problem, area served, workflow, and handover expectation. Do not make every service page a lightly edited copy of the same pitch.
Guides and topic hubs
Use guides for practical advice and topic hubs to connect related articles. This gives search engines and visitors a clearer map of the site.
Proof pages
Link projects, repositories, screenshots, case studies, and profile pages so professional claims are checkable instead of just asserted.
Page cluster
Give each ranking asset a different job
One domain can earn several useful results when the pages are genuinely different. The clean pattern is not duplication: it is a homepage, service pages, location/profile pages, guides, project notes, and tools that answer different questions.
Identity page
Use About and profile pages to confirm the person, location, professional context, and trusted owned links.
Service-intent page
Use service pages for a specific problem and workflow: website support, SEO foundations, IT support, Microsoft 365, DNS/email, or networking.
Guide page
Use guides to answer practical questions in depth, with examples, checklists, and internal links to the most relevant support pages.
Proof page
Use projects, source archive, screenshots, case studies, and public repositories to make capability claims checkable.
Measurement
Measure crawl and visibility without overreacting
Search results move slowly and can vary by device, location, capitalisation, browser history, and Google interface features. A useful measurement habit is to record dated checks, then improve pages based on patterns rather than one surprising search.
After publishing
Check the live URL, canonical tag, sitemap entry, internal links, and structured data before assuming Google has a clean page to crawl.
After crawl time
Use Search Console where available to compare impressions, indexed status, queries, and page-level movement against the date of the change.
Before adding more pages
Look for pages that are thin, duplicated, orphaned, or unclear. Improving existing assets is often better than publishing another weak URL.
Google checks
Use Search Console as a diagnostic tool, not a magic button
Search Console is useful because it separates crawl, indexing, canonical, sitemap, and structured-data signals. It does not guarantee rankings, but it tells you whether Google can see the page cleanly enough to evaluate it.
URL Inspection
Inspect important URLs after major changes to check indexed status, live-test eligibility, selected canonical, and crawl/indexing issues.
Sitemap consistency
List canonical, indexable URLs in the sitemap. Do not mix sitemap URLs with different canonical URLs for the same page.
Canonical consistency
Use redirects, canonical tags, sitemap URLs, and internal links to point at the same preferred version of each important page.
Structured data
Use structured data to clarify visible facts about the page. Validate JSON-LD after deployment because a small syntax error can break the signal.
Use the path
Build a site that can be checked by people and crawlers
The useful pattern is simple: publish the right page, link it from the right places, make the canonical URL unambiguous, and keep enough measurement evidence to know whether Google has seen the change. This is slower than chasing quick tricks, but it leaves cleaner assets behind.
Launch checks
Confirm the page returns 200, has one canonical URL, uses a useful title and description, and is linked from a relevant hub.
Search checks
Update the sitemap, inspect crawl/index state where available, and record dated measurements rather than relying on one personal search.
Content checks
Make each page answer a distinct intent, avoid duplicate doorway pages, and add practical examples before adding more URLs.
Proof checks
Keep screenshots, source links, project notes, and public profile links aligned so a visitor can verify the work without guesswork.
Related support
Where the practical work lives
These pages are the hands-on follow-up when you need to fix the underlying systems: domains and routing, website ownership handover, and an SME upgrade workflow that can be done without chaos.
Route the work
Pick the next page based on the search problem
Website and search work gets clearer when the next step is tied to evidence: launch state, crawl/indexing state, service-page structure, project proof, or the practical systems behind the website.
SEO consulting NZ
Use this service page when the work is crawl/indexing triage, canonical cleanup, metadata, internal links, local entity basics, or handover notes.
Technical SEO audit checklist
Use the audit checklist when the page needs a concrete pass across canonicals, redirects, sitemap coverage, structured data, and internal links.
Website launch checklist
Use the launch checklist when the problem is forms, redirects, analytics, sitemap discovery, backups, or post-launch verification.
SME tech upgrades
Use the upgrade page when website work overlaps with email, phones, forms, Microsoft 365, devices, or general handover cleanup.
Launch checklist tool
Use the interactive tool to capture launch checks, notes, and handover items before or after a site change.
Google Business Profile checklist
Use the profile checklist when local visibility depends on consistent business details, service areas, photos, reviews, and profile accuracy.
public source archive SEO proof
Use this path when project sites, repositories, screenshots, case studies, and profile links need to reinforce each other.
Services overview
Use the services hub when the search issue crosses into DNS/email, Microsoft 365, remote support, networking, fibre, or VoIP.
Operational handoff
Turn search notes into checkable work
Website visibility improves fastest when every observation becomes a checkable change: which URL changed, which signal was affected, how it was validated, and which hub or service page now points to it.
Tools hub
Use the tools hub when the next step is a reusable checklist for launch notes, business profile details, reviews, or recurring maintenance.
Launch checklist tool
Use this tool to capture canonicals, redirects, forms, analytics, sitemap, backups, and post-launch verification in one place.
Maintenance calendar tool
Use the calendar when search work creates recurring checks for sitemap health, profile accuracy, backups, DNS/email, and analytics.
Domains, DNS, and email
Use this path when search or launch work depends on registrar control, DNS ownership, mail routing, form delivery, or rollback notes.
SEO consulting NZ
Use the service page when the evidence points to crawl/indexing triage, structured data, metadata, internal links, or local entity cleanup.
Services overview
Use the services hub when a search issue crosses into Microsoft 365, email deliverability, DNS/routing, networking, or general IT support.
Context
Project and professional evidence
For current professional context, start with About. For software-development proof, use the Projects hub and case studies.