Field note 02 · Technical SEO
Technical SEOBefore Google Indexing
GrowthFlint’s pre-indexing technical SEO process: crawl access, canonicals, sitemaps, redirects, private-page protection, metadata, schema and live validation.
Turning on search visibility is not the same as being ready for Google. Before we ask Google to crawl and index a production site, GrowthFlint checks whether the public pages are accessible, internally consistent and safe to expose. The aim is to avoid sending mixed signals at the exact point search engines begin learning the site.
Section 01
1. Confirm the site is intentionally public
WordPress has a search-engine visibility setting that is useful during development but dangerous if forgotten after launch. We confirm the production site is public and that robots.txt is not using a root-wide disallow rule.
At the same time, we do not assume every URL should be public. Customer-specific project, proposal, payment or tracking URLs can remain protected while the main marketing site is crawlable.
Section 02
2. Check the preferred version of every important URL
A site should have a consistent HTTPS and hostname strategy. We verify that HTTP redirects to HTTPS and that the chosen www or non-www version is consolidated. Canonical tags should point to the intended public URL rather than a staging address, tracking URL or accidental duplicate.
We also test a URL with query parameters to make sure tracking parameters do not create a second canonical version of the homepage.
Section 03
3. Make the sitemap useful rather than simply present
A sitemap is a discovery aid, not a list of everything WordPress can generate. We review which URLs are included and remove unnecessary author, empty taxonomy or bridge pages when they add no search value. Public service pages should be discoverable; temporary or private utility pages should not be promoted through the sitemap.
Section 04
4. Verify headings and metadata on real live pages
Technical readiness includes what the crawler actually receives. We check that a main page has one clear H1, a useful title, a descriptive meta description and a canonical URL. These checks are performed against the live output rather than only trusting what an editor screen says.
Section 05
5. Validate structured data without inventing claims
Structured data can help machines understand the business and page relationships, but it should describe information that genuinely exists. We prefer stable Organization and WebSite identities, clear service relationships and breadcrumbs. We avoid fake ratings, fabricated reviews and markup that promises a rich result Google does not support.
Section 06
6. Test a real 404 and private-page boundaries
A missing URL should return a real 404 status. Soft-404 behavior can confuse crawlers and users. We also check that private customer URLs carry noindex protection so search visibility for public pages does not accidentally expose customer workflows.
Section 07
7. Use Google’s own tools after the internal checks
Once the site passes our internal checks, we verify ownership in Google Search Console, submit the sitemap and use URL Inspection on priority pages. A green live test confirms that Google can access the current page; a request for indexing asks Google to consider recrawling it but does not guarantee ranking or immediate inclusion.
Section 08
Questions we answer before indexing
Should every page be submitted manually?
No. Manual URL requests are useful for a small set of important pages, but sitemap discovery and normal crawling remain the scalable foundation.
Does a green live test mean the page will rank?
No. It means the page is technically available to Google under the conditions tested. Ranking depends on relevance, quality, competition and many other signals.
Why check this before content promotion?
Because authority work is wasted if search engines first encounter blocked, duplicated or inconsistent URLs. A clean foundation gives later content and links a stable destination.
Technical SEO before indexing is quality control. It does not manufacture rankings; it makes sure the site is giving search engines a coherent, intentional version of the business to crawl.
Connected capabilities
Explore the work behind this note.
The article explains the thinking. These are the GrowthFlint services most directly connected to the work.
Advanced SEO Services
Technical, on-page and discovery work designed to make important pages easier to crawl, understand and find.
FocusTechnical SEO · On-page · AI Discovery
OutcomeBuild visibility around systems search can understand.
Build visibility around systems search can understand.
View serviceWordPress Website Development
Fast, conversion-focused business websites built around clear journeys, performance and search-ready foundations.
FocusWordPress · UX · Performance
OutcomeLaunch on a foundation built to grow.
Launch on a foundation built to grow.
View serviceMaintenance & Performance
Ongoing technical care for critical sites that need dependable updates, speed, stability and controlled change.
FocusUpdates · Performance · Stability
OutcomeKeep important websites fast, stable and ready to evolve.
Keep important websites fast, stable and ready to evolve.
View serviceKeep exploring
Explore more Field Notes.
Every other published GrowthFlint Field Note, kept in one connected library.
From Insight to Action
Clearer thinking. The right next move.
Explore the capability that fits your situation, or start a project when you already know what needs to change.