Technical SEO Checklist Before You Publish
A practical preflight for Next.js and WordPress launches so Google can crawl what you shipped.
“Beautiful pages that are noindexed help no one.”
Publishing without a technical SEO pass is how good content stays invisible. weROI runs a practical checklist before Jamaican and worldwide sites go live or ship major pages: crawlability, index rules, speed, structured data, and Search Console readiness. A publish gate sounds bureaucratic until you watch a staging noindex silently follow a redesign into production and erase weeks of work.
Use this checklist as a gate before you hit publish. It is written for founders and marketers who need a clear pass or fail, not a research paper. Fix blockers first, then polish copy, so Google and humans can both reach the work you just finished. Run the checklist even when you are late. Invisible pages help no campaign calendar.
Crawl and index basics
Confirm robots.txt is not blocking critical paths on production. Check that staging noindex did not follow you to live. Verify canonical tags point to the preferred URLs. Soft-404s and accidental duplicates waste crawl budget and confuse rankings.
Generate a clean XML sitemap of indexable URLs and submit it in Search Console. Spot-check a sample of new pages with URL inspection. Kingston launches often stumble when a developer flag meant for preview stays on.
Compare the live robots.txt to what you intended. One disallow line aimed at a preview path can accidentally blanket sections you need crawled.
Before you celebrate a launch on social, confirm the production hostname is the one verified in Search Console and that analytics is firing on the money pages you just published. Hostname mismatches are a quiet way to lose weeks of learning.
Titles, headings, and unique content
Every URL needs a job
Each published page needs a unique title, a clear H1, and body content that is not spun from another parish template. Thin doorway pages hurt more than they help. If two URLs compete for the same intent, consolidate or differentiate honestly.
Internal links from existing hubs should point to the new page with descriptive anchors. Orphan pages are easy to ship and hard to discover. weROI includes internal link tasks in the publish checklist on purpose.
Orphan pages are common after redesigns. From each new money URL, ensure at least two internal links from pages that already earn traffic.
Speed and mobile readiness
Test on mid-range Android and realistic mobile data. Compress images, lazy-load below-the-fold media, and avoid autoplay video in the hero by default. Core Web Vitals are not vanity when bounce is expensive.
Tap targets for WhatsApp and call must work with thumbs. Technical SEO that ignores conversion paths is incomplete for service businesses in Jamaica.
Retest after tag-manager changes. Marketing pixels sometimes reintroduce heavy scripts that undo a careful performance pass.
When multiple developers touch templates, require a short checklist sign-off in the pull request: indexability, title uniqueness, and CTA tap targets. Cultural enforcement beats heroic fire drills after Google already crawled the wrong version.
Structured data and rich result hygiene
Add Organization, Service, FAQ, and BlogPosting schema where it fits and stays accurate. Validate before launch. Do not mark up reviews you do not have or offers that are not on the page. Fake schema is a trust risk.
Schema must match visible content. Marking up FAQs that are not on the page is a shortcut that creates risk without durable gain.
- HTTPS everywhere with no mixed content
- Canonical and hreflang only when you truly need language or region variants
- 404 and redirect maps for replaced URLs
- Open Graph tags that match the visible title and image
- Analytics and Search Console connected on production domains
Security, spam, and form integrity
Confirm forms submit, spam protection does not block real humans, and thank-you states do not create indexable junk URLs. Check that private tools and client portals remain noindex. A publish checklist should include a quick security glance, not only keywords.
For worldwide audiences, confirm timezone and currency statements on commercial pages are accurate. Technical readiness includes content accuracy that prevents bounce after the click.
Confirm thank-you URLs are noindex when they are thin. Indexable thank-you stubs create confusing duplicates beside the real service pages.
If you publish multilingual or multi-region variants later, revisit this gate. hreflang mistakes and duplicate English clones create the same class of problems this checklist exists to prevent.
Post-publish monitoring window
Watch coverage, crawl stats, and query appearance for two weeks after major launches. Fix soft errors quickly. Document what shipped so the next release reuses the same gate. Technical SEO is a habit at weROI, not a ceremony once per year.
Keep a shared launch channel note: what shipped, who verified Search Console, and when the two-week watch ends.
Practical steps you can take this week
Run this gate on every major publish, including redesign cutovers.
- Verify robots, canonicals, and noindex status on production for the new URLs. Screenshot the verification for the launch record.
- Confirm unique titles, H1s, and at least two internal links into each new money page. Check that H1 and title describe the same job.
- Compress media and test load plus CTA taps on a mid-range phone. Use a mid-range Android on mobile data if you can.
- Validate relevant schema and Open Graph tags against page content. Fix mismatches before announcing publicly.
- Submit or refresh the sitemap and inspect a sample URL in Search Console. Resubmit only after the sitemap reflects production.
- Calendar a two-week check for coverage errors and unintended duplicates. Put the watch on the team calendar with an owner.
FAQs
Do I need this checklist for a blog post?
Yes in lighter form: unique title, internal links, images, indexability, and Search Console awareness. Full migrations need the heavier gate. Skipping basics is how posts never appear. Blog posts still need unique titles, links, and indexability even when the gate is lighter.
What if developers own the stack?
Share this checklist as acceptance criteria. Marketing still owns confirming titles, intent, and conversion paths. Joint ownership prevents finger pointing after launch. Joint acceptance criteria prevent the classic marketing versus engineering blame loop.
Are Core Web Vitals a ranking absolute?
They matter for experience and can influence visibility, but content relevance still rules. Do not ignore speed. Also do not obsess over tiny lab scores while the page cannot convert. Relevance still rules, but slow money pages tax every click you already paid for.
Should staging be indexed?
No. Protect staging with auth and noindex. Confirm production is the opposite before announcing a launch. Auth plus noindex on staging is cheaper than cleaning a mess after Google notices.
Can weROI run pre-publish audits?
Yes. Technical SEO reviews are part of our SEO and website engagements for Jamaica and remote clients. We often pair the gate with content and CTA checks so technical wins convert.
Post-launch technical monitoring
Watch Search Console for coverage errors, spike in 404s, and unexpected noindex. Re-test LCP after content editors upload huge images. Technical SEO is a launch gate and an ongoing hygiene habit.
Keep a redirect map for any URL changes during content migrations. Beautiful new paths mean nothing if old backlinks die.
Going deeper on Technical SEO Checklist Before You Publish
This section expands practical guidance for teams working with weROI on seo initiatives across Jamaica and worldwide remote delivery. Use it as an operating checklist beside the steps above.
Search visibility compounds when technical health, on-page clarity, and conversion paths improve together. Kingston businesses and worldwide remote clients both benefit when money pages answer a single intent with FAQs, proof, and a human next step.
Key takeaways
- Gate every major publish on crawl, index, and unique intent
- Test speed and CTAs on real mobile conditions
- Use accurate schema and connect Search Console before celebrating
- Monitor coverage for two weeks after launch