Before a new WordPress site goes live, SEO has a batch of switches you’ll regret not setting. Most are one-time configurations, yet they decide the foundation of future indexing and rankings; missing any one means after-the-fact remediation at higher cost.
The complete system lives in the technical SEO handbook; this article focuses on the must-configure checklist you should tick off item by item before launch.
Permalink structure
WordPress’s default links are ugly parameter addresses like /?p=123 — unfriendly to both crawlers and users. Before launch, switch to a clean structure like “post name” or “date plus post name,” and addresses immediately become readable and keyword-bearing. This change costs zero but affects the URL quality of every page on the site — the number-one must-configure.
After changing, make sure the old default format is no longer accessible or is 301’d, to avoid two sets of addresses coexisting. If the site already ran before the change, you need to plan redirects for old links. For a new site, decide it while the site is empty — easiest. Once the link spec stabilizes, all future content benefits automatically without per-page rework; it’s the first item to tick on the launch checklist.
Sitemap and submission
Generate an XML sitemap with an SEO plugin, list important pages for search engines, and submit it in Search Console. It doesn’t guarantee indexing, but it’s the clearest “please crawl these” signal — especially useful for new sites with no backlinks. Make sure the map auto-updates with content, not a one-time dead file.
Also check whether robots.txt allows the sitemap path and hasn’t wrongly blocked key directories. The map and robots are a pair; miss one and the signal weakens. After submitting, watch the “discovered/indexed” trend in the console as the first verification that the new site is being recognized correctly — spotting anomalies earlier than waiting for rankings.
Title and description templates
The title tag is key to rankings and clicks. Set up a template (like Post Title | Site Name) so every page has a unique, keyword-bearing title — don’t let the program leave blanks or use the same default name. Descriptions don’t directly affect rankings but do affect CTR in results; a good template mass-produces decent snippets, saving per-piece manual writing.
Avoid all pages sharing the same title or description — that’s a classic duplicate signal, making it hard for engines to distinguish page topics. Use variables in the template (title, category, page number) to guarantee differentiation. Set once and all thousand pages automatically comply — one of the highest-ROI WordPress SEO configurations, worth tuning carefully before launch.
Index control: index only what should be indexed
New sites often have pages that shouldn’t be indexed: admin, search results, tag archives, test pages. Block them with noindex or robots to avoid index bloat and weight dilution early on. The principle is “default open indexing only to truly valuable content,” not letting the whole site be indexed in one go.
This ties closely to crawl budget optimization: a new site is already thin on weight and crawling; wasting budget on valueless pages makes core content harder to crawl. Writing “which types don’t get indexed” as a rule before launch beats cleaning up afterward — it also stops low-quality pages stealing core pages’ limelight and keeps the foundation cleaner.
Structured data and Open Graph
Add structured data to articles and products (like Article, breadcrumbs, Organization) to help search engines understand content and win rich-media displays. Open Graph tags for social sharing (title, image, description) decide how links look on social platforms. Both are one-time configs that improve presentation long-term — worth laying out before launch.
Don’t stack irrelevant markup; only mark content that really exists, or you risk being judged as abuse. Use plugin or theme built-in capabilities rather than hand-writing complex code. Structured data is “icing” rather than “lifeline”; its priority ranks after links, indexing, and speed — but configuring it at launch saves make-up lessons later.
Speed and security baseline
Before launch, confirm caching is installed, compression is on, and images are optimized — don’t let the speed baseline be too ugly. A new site’s first impression matters; a slow site loses at the starting line. Also enable HTTPS and fix any mixed content; a secure site helps both rankings and trust, and certificates are mostly free now — no excuse not to.
Also confirm “discourage search engines” is turned off — a switch often left on during development; forgetting it means the whole site isn’t indexed, the most embarrassing low-level mistake. Write it into the launch checklist and tick it with the other items to block most “launch-time disasters” and get a steady start.
Launch checklist
Turn the above items into one tick-off table, confirm each before launch, and run it in the test environment first. The table at minimum includes: permalinks, sitemap submission, title templates, noindex rules, structured data, HTTPS, and turning off discourage-indexing. Whoever launches ticks it; only release after it’s fully ticked — this blocks most low-level incidents, far steadier than relying on memory.
The checklist grows with the site (like whether a newly added channel should be indexed, whether new content types need structured data). It’s the team’s shared memory, preventing “the landmine stepped on last time gets stepped on again.” Ten minutes of ticking before launch saves days of firefighting after — the return on this zero-cost investment only shows its value the moment something goes wrong.
Common omissions
The easiest things to forget are the details: forgetting to turn off discourage-indexing so the whole site isn’t indexed, forgetting the homepage title template so all pages share a name, forgetting to block search-result pages so the index bloats. List these small-but-fatal items at the top of the checklist and force confirmation before launch — blocking most disasters, far more reassuring than after-the-fact fixes.
Figure: Must-Configure Before Launch — Key Points (compiled by YunyingGO)
| Item | Setting | Reason |
|---|---|---|
| Permalinks | Post name | Clean URLs |
| Sitemap | Auto-generated | Guide crawling |
| Title templates | Differentiated | Prevent duplicates |
| Indexing | noindex valueless | Save budget |
| HTTPS | Enabled | Security and rankings |
When you wrap up, follow these steps: change permalinks to post name and eliminate the default ?p= format; generate and submit the XML sitemap; set up title/description templates so every page is differentiated; use noindex/robots to block valueless pages; finally confirm “discourage indexing” is off and HTTPS is enabled. Once these are done, the new site’s SEO foundation is solid, and future content fills in without drifting off track.
