WORDPRESS SEO / BEFORE THE WEBSITE GOES LIVE

WordPress SEO: What Should Be Built Into the Website Before Launch?

If search visibility matters to your business, SEO cannot be a task that starts after the website is finished. The page structure, URLs, content hierarchy, internal links, metadata, redirects and measurement setup all need to be considered while the site is being built.

Alpha WordPress Design Perth 14 September 2026 13 min read

THE SHORT ANSWER

A new WordPress website should launch with its search foundation already in place.

That means more than installing an SEO plugin. Before launch, the site should have a deliberate page architecture, unique titles and headings, crawlable content, sensible internal links, canonical signals, clean indexation settings, redirect mapping where URLs change, structured data where it genuinely applies, analytics and Google Search Console connected to the live site.

Before designMap intentDecide which searches and customer decisions deserve their own pages
During buildMake it crawlableKeep important content accessible, internally linked and technically indexable
Before launchProtect URLsMap redirects, canonicals and indexation settings before the domain changes
After launchMeasure realityUse Search Console and analytics to see what users and Google actually do

The strongest time to make an SEO decision is usually before the page exists, not after traffic has already been lost or the wrong structure has been indexed.

A WordPress website can look polished and still launch with weak search foundations. Important services may be buried on one page, several URLs may target the same intent, navigation may not show which pages matter most and a redesign may quietly remove URLs that already earned visibility.

Those problems are harder to repair once the site is live because the architecture, design and content have already been approved around them. Search strategy therefore belongs inside planning, content and development — not in a separate checklist added at the end.

The aim is not to make every page chase a keyword. It is to give each useful page a clear job, make the relationship between pages obvious, preserve existing value where it exists and create a measurement setup that tells you what deserves improvement after launch.

01 / SEARCH INTENT BEFORE SITEMAP

Decide what each page needs to answer before you decide what goes in the menu

A clean sitemap begins with customer intent. Page count comes later.

01

Separate genuinely different decisions

A customer looking for WordPress maintenance is making a different decision from someone looking for a new ecommerce build. Those intents usually deserve separate pages because the proof, scope, objections and next action are different.

One useful page per distinct intent
02

Do not split synonyms into thin pages

Creating separate pages for near-identical phrases usually gives the site more URLs without giving the visitor more value. Stronger pages consolidate overlapping language around one clear purpose.

Depth before duplication
03

Keep commercial pages easy to find

Primary services, key industries, useful locations and conversion pages should not depend on a search engine discovering an orphan URL. Navigation and internal links should make the important paths obvious.

Discovery through real links
04

Use the blog to support, not compete

Informational guides should answer research questions and then connect readers to the relevant service or decision page. They should not duplicate the same commercial target with a longer article.

Content supports money pages

02 / ON-PAGE FOUNDATIONS

Every important page should launch with the basics already resolved

These are simple elements, but inconsistency across dozens of pages can make a site much harder to understand and maintain.

01

A clear title and H1

The browser title and main page heading should describe the actual page, not repeat the same generic brand phrase everywhere.

02

Useful headings that match the buying journey

Sections should help people scan the page and understand scope, proof, pricing, process, risks and next steps — not exist only to insert variations of a keyword.

03

A concise meta description

Write a useful summary for the searcher. Google may choose another snippet from the page, but a strong description still gives the page a clear default.

04

Descriptive image alt text where it helps

Alt text should explain meaningful images for accessibility and context. Decorative artwork does not need to become a keyword list.

05

Consistent URL structure

Keep URLs short, readable and stable. If a page already has a useful URL with search history, change it only when there is a clear reason and a redirect plan.

06

A visible next step

Search traffic has little commercial value if the page answers the question but never shows the visitor where to compare services, see proof or start a conversation.

03 / INTERNAL LINKING IS SITE ARCHITECTURE

Internal links should show the relationship between your services, proof, locations and guides

The goal is not to add links everywhere. It is to make the path between related decisions clear.

01

Service → proof

A service page should be able to point to relevant portfolio work, reviews or case studies so the visitor can validate the capability behind the claim.

Connect claims to evidence
02

Guide → commercial page

A pricing, platform or SEO guide should link to the service that can solve the problem when the reader is ready to move from research to action.

Support the next decision
03

Location → strongest service

A Perth location page should connect to the services genuinely offered in that market rather than competing with the main service pages for the same purpose.

Local context, central expertise
04

Related pages → related language

Anchor text should tell the visitor what they will reach. Generic “click here” links waste useful context when the destination can be described naturally.

Descriptive anchor text

04 / TECHNICAL INDEXABILITY

A page cannot earn search visibility if the launch setup quietly tells crawlers to ignore it

Before launch, we check the signals that decide whether useful content can be discovered, rendered and indexed as intended.

01

Check robots and noindex settings

Staging sites are often blocked from indexing. That protection needs to stay on staging and come off the live pages that should appear in search.

02

Confirm canonical URLs

Each indexable page should point to the preferred version of itself unless there is a deliberate reason to consolidate it elsewhere.

03

Keep important content in the rendered page

Customers and search crawlers should be able to access the meaningful text, links and headings without depending on fragile interactions or hidden application states.

04

Generate and submit the sitemap

The XML sitemap should contain the live canonical URLs you actually want discovered, then be submitted through Search Console after launch.

05

Test status codes and error handling

Published pages should return 200, moved URLs should redirect correctly, and missing content should not masquerade as a successful page.

05 / REDESIGNS NEED A URL PLAN

If an existing website already ranks, the new design should know what it is replacing

A redesign is one of the easiest moments to lose search value because URLs, content and internal links often change together.

Before a redesign goes live, we compare the old and new URL sets. Pages that still serve a useful purpose should either retain their URL or move to the closest relevant destination through a permanent redirect.

A redirect should not send every removed page to the homepage. The destination needs to make sense for the user who expected the old page. When no relevant replacement exists, keeping a clean 404 can be more honest than forcing unrelated content.

We also check whether important headings, copy, internal links and page purposes have been removed during the visual redesign. A cleaner layout is useful; stripping away the information that made a page valuable is not.

  • Export the existing indexable URLs before launch
  • Keep high-value URLs stable where practical
  • Map every intentional URL change to the closest useful destination
  • Update internal links so the site points directly to the new URLs
  • Check Search Console after launch for indexing and crawl issues

06 / STRUCTURED DATA

Schema should describe what is genuinely on the page — not manufacture eligibility for a rich result

Structured data can help search engines understand entities and page types, but only when the markup matches the visible content.

USE SCHEMA AS DESCRIPTIONAdd the markup that fits the page you actually have, validate it and keep the visible content consistent with the data.

For this website that can include WebPage, BreadcrumbList, Article or BlogPosting on guides, and other supported types where the real page content qualifies. We do not add review ratings, FAQs, business details or other claims that are not actually present and supportable.

07 / MEASUREMENT BEFORE MARKETING

Connect the website to real performance data before you start judging whether SEO is working

A launch without measurement turns every future SEO conversation into guesswork.

01

Google Search Console

Verify the property, submit the sitemap and use Search Console to see queries, pages, indexing issues and the URLs Google actually recognises.

Search visibility data
02

GA4 or your analytics stack

Track useful behaviour such as enquiries, calls, form submissions, purchases or other actions that matter to the business rather than treating page views as the only outcome.

Behaviour and conversions
03

Conversion events

The primary contact forms, ecommerce actions and other high-value interactions should be tested on the live site so the numbers are trustworthy from launch day.

Measure commercial actions
04

Baseline before major changes

For redesigns, retain enough pre-launch data to compare landing pages, search clicks and conversions after the new site is live.

Know what changed

08 / PERTH LOCAL SEO

Local SEO should reflect the markets you genuinely serve, not produce a page for every suburb on a map

Perth-wide visibility comes from useful service pages, credible business details, real local relevance and selected location content where the intent is distinct.

A business serving Joondalup, Subiaco, Fremantle or Rockingham does not automatically need four copies of the same page. A location page earns its place when it can answer a different local search need with genuine service coverage, nearby context, proof and a useful route back to the relevant service.

For businesses with a real office or storefront, consistent name, address, phone and Google Business Profile information matter. Service-area businesses should represent their actual operating model accurately rather than creating addresses or location claims they cannot substantiate.

Perth CBDSubiacoFremantleJoondalupOsborne ParkWannerooMidlandCanningtonRockingham

09 / THE PRE-LAUNCH SEARCH CHECK

Before the DNS changes, these are the questions we want answered

The purpose is not a perfect score. It is to remove avoidable launch problems while the site is still easy to change.

01

Does every important page have a clear purpose?

If two pages answer the same customer question, decide whether they should be consolidated before both are indexed.

02

Can the important pages be reached through normal links?

Navigation, hubs and contextual links should expose the pages the business actually wants customers and search engines to find.

03

Are titles, headings and metadata unique where they should be?

Repeated generic metadata makes it harder to understand what is different about each page.

04

Are old URLs protected?

For redesigns and migrations, test redirect mappings before launch rather than discovering missing pages after traffic drops.

05

Are analytics and Search Console ready?

Measurement should be tested before launch so post-launch comparisons begin with clean data.

06

Can the live site actually be indexed?

Check robots, noindex, canonical, HTTP status and sitemap behaviour on the production environment.

10 / THE FIRST 30 DAYS AFTER LAUNCH

SEO does not stop at launch — that is when the first reliable feedback arrives

The new site gives you real crawl, impression and conversion data. Use it to find the next highest-value improvement.

01

Check indexing and crawl signals

Review Search Console for submitted versus indexed URLs, unexpected exclusions, canonical differences and crawl problems.

02

Watch the important landing pages

Compare impressions, clicks, engagement and conversions on the pages that matter most instead of reacting to one site-wide traffic number.

03

Fix broken journeys quickly

Test forms, phone/email links, ecommerce actions and key internal links again on the live domain.

04

Improve pages with evidence

Where a page earns impressions but weak clicks or attracts traffic without enquiries, refine the message, proof, snippet and conversion path around the behaviour you can see.

05

Build the next content gap deliberately

Use real query and customer data to decide which service detail, guide, case study or location content deserves to be created next.

WORDPRESS SEO BEFORE LAUNCH FAQS

Questions businesses usually ask before an SEO-ready WordPress launch

These answers separate the work that belongs inside the build from the ongoing work that continues after the site is live.

06 QUESTIONS

Clear answers to the decisions that usually affect cost, scope and ownership.

ANSWER

No. A plugin can help manage titles, canonicals, sitemaps and other settings, but it cannot decide your service architecture, write useful content, create internal relationships between pages or preserve valuable URLs during a redesign. The strategy and implementation still need human decisions.

ANSWER

The important structural SEO decisions should happen before or during design. Search intent, sitemap, page purpose, content depth and internal linking affect the layout and navigation. After launch, SEO continues through measurement, content improvement, authority building and new opportunities.

ANSWER

Some pages can be discovered and indexed quickly, but meaningful rankings depend on competition, relevance, site history, authority, content quality and many other signals. A technically clean launch removes avoidable barriers; it does not create a ranking guarantee.

ANSWER

No. Group closely related wording around the same useful intent. Create a separate page when the visitor needs materially different information, proof or action — not simply because a keyword tool lists another phrase.

ANSWER

At minimum, verify Google Search Console, submit the XML sitemap and connect the analytics platform you use for business reporting. Important enquiry, call or ecommerce actions should be tested so the data is useful from the first day.

ANSWER

It can if valuable URLs disappear without a sensible replacement. When a URL genuinely needs to change, map it to the closest relevant destination with a permanent redirect, update internal links and monitor the change in Search Console after launch.

PLANNING A WEBSITE THAT NEEDS TO EARN SEARCH VISIBILITY?

Bring us the services, current rankings and customers you want the new site to reach — we will build the search architecture into the project before the design is locked.

Share your current website, priority services, Perth markets, existing SEO concerns and what you want the new site to achieve. We can turn that into a practical WordPress structure, migration plan and launch measurement setup.