--- title: "Build organic search into your technical architecture before the fixes get expensive" description: "Choose rendering, URL, crawl, performance, and structured data patterns that search engines can index, and build SEO checks into the engineering workflow." canonical: "https://scalewithsearch.com/articles/seo-for-ctos" date: "2026-03-20" modified: "2026-09-25" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Real estate - Real estate - [Real estate](https://scalewithsearch.com/for/real-estate) - Work - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief) - Build - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work) - For your business - Trades and home services - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops) - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair) - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors) - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors) - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning) - [Locksmiths](https://scalewithsearch.com/for/locksmiths) - [Moving companies](https://scalewithsearch.com/for/moving-companies) - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies) - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors) - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage) - [Roofing companies](https://scalewithsearch.com/for/roofing-companies) - [Towing companies](https://scalewithsearch.com/for/towing-companies) - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping) - [Solar installers](https://scalewithsearch.com/for/solar-installation) - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction) - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving) - Practices and professional services - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices) - [Dental practices](https://scalewithsearch.com/for/dental-practices) - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms) - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics) - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms) - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics) - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness) - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health) - [Medical billing companies](https://scalewithsearch.com/for/medical-billing) - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies) - [Financial advisors](https://scalewithsearch.com/for/financial-advisors) - [Property management companies](https://scalewithsearch.com/for/property-management) - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing) - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers) - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain) - Agencies, MSPs, and manufacturing - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers) - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing) - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers) - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants) - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators) - Restaurants, shops, studios, and nonprofits - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality) - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce) - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers) - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits) - [All industries](https://scalewithsearch.com/for/) - Learn - For your office - [Office job guides](https://scalewithsearch.com/guides/) - [Browser calculators](https://scalewithsearch.com/tools/) - Start here - [How it works](https://scalewithsearch.com/how-it-works) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip) - Guides - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles by cluster - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - For machines - [llms.txt](https://scalewithsearch.com/llms.txt) - [llms-full.txt](https://scalewithsearch.com/llms-full.txt) - [Machine view](https://scalewithsearch.com/?view=machine) - Company - Evidence - [Proof](https://scalewithsearch.com/proof) - Company - [About](https://scalewithsearch.com/about) # Build organic search into your technical architecture before the fixes get expensive. A product team ships a new marketing site as a client-rendered single page application. Six months later, marketing asks why half the pages are not in Google. The answer sits in an architecture decision that nobody reviewed for search. Technical decisions made during product development create SEO advantages or liabilities that last for years. Many CTOs find the problems late. By then the architecture has set, and the team has tuned for internal metrics that conflict with search. Competitors have also won rankings with better implementations. This article covers the decisions to get right early and the process that keeps them right. ## Make architecture decisions with search in mind ### Choose a rendering strategy that crawlers can read A single page application (SPA) built with React, Vue, or Angular renders content in the browser. Until JavaScript runs, a crawler sees incomplete HTML. Google renders JavaScript, but rendering happens in a later pass, so JavaScript-heavy pages are often indexed later than server-rendered pages. Server-side rendering (SSR) and static site generation (SSG) avoid the problem. Next.js, Nuxt, and SvelteKit generate complete HTML on the server, so crawlers get the content at once. SSR adds infrastructure and server load. SSG renders pages at build time, which removes runtime rendering cost and keeps pages crawlable. The most common architecture mistake is a pure client-rendered SPA for public content. Teams optimize for developer experience and speed of delivery and rely on Google's renderer for the rest. In practice, client rendering delays indexing, uses more crawl capacity, and makes rankings depend on Google's rendering pipeline. Choose SSR or SSG from the start unless the application sits entirely behind a login. [Server-side rendering for SEO](/articles/server-side-rendering-seo) compares the options in detail. ### Keep public content on one domain Microservices often split public content across origins. The blog lives at `blog.example.com`, products at `www.example.com/products`, and documentation at `docs.example.com`. Search engines can treat each subdomain as a separate site, so the split can divide authority. Consolidate user-facing content under one domain where you can. Use subdomains only for genuinely separate services, such as a customer support portal. ### Render API content into HTML An API-first architecture gives front-end flexibility. If content exists only in API responses, with no HTML representation, search engines cannot index it. Feed content APIs into a server rendering layer that produces crawlable HTML. Or use a hybrid: render critical content on the server and load interactive features in the browser. ### Choose a CDN for performance Cloudflare, Fastly, and Akamai differ in edge caching, DDoS protection, and global points of presence. Choose a CDN with HTTP/2 or HTTP/3, Brotli compression, and image optimization. A poor CDN choice adds latency, which shows up directly in Core Web Vitals. ## Manage crawl capacity on large sites Crawl budget is the number of pages a search engine crawls on your site in a given period. [Google's crawl budget guide](https://developers.google.com/search/docs/crawling-indexing/large-site-managing-crawl-budget) targets two rough groups. One is sites with more than a million pages that change weekly. The other is sites with more than 10,000 pages that change daily. On those sites, some pages are seldom crawled, and updates take longer to appear. ### Control access with robots.txt and authentication Block URL spaces that add no indexable content: internal search results, and faceted navigation such as `/products?color=red&size=large&brand=nike`. Each parameter combination uses crawl capacity without adding a unique page. Do not use robots.txt to hide sensitive areas. The file is public, so a `Disallow: /admin/` line tells attackers where the admin interface is. Protect admin areas and user accounts with authentication. For pages that must stay out of the index, use a `noindex` robots meta tag or an `X-Robots-Tag` header. [Robots.txt and crawl budget for developers](/articles/robots-txt-crawl-budget-developers) covers the directives. ### Segment the XML sitemaps Do not submit one sitemap with 50,000 URLs. Split sitemaps by content type: products, blog posts, category pages, and static pages. Regenerate the relevant sitemap as soon as priority content publishes. List only public, indexable URLs. A sitemap is also public, so it must not reveal admin interfaces, private beta features, or other sensitive paths. ### Keep important pages close to the homepage Pages linked from the homepage and main navigation are crawled often. Pages four or more clicks deep are crawled rarely. Use breadcrumbs and contextual internal links to keep important pages within three clicks of the homepage. Server log analysis shows live pages that get no crawls at all; each one is an internal linking failure. ### Remove duplicate URL variants Tracking parameters, session IDs, and sort options can make one product page reachable at many URLs. Add a canonical tag that names the preferred URL. Google [retired the URL Parameters tool](https://developers.google.com/search/blog/2022/03/url-parameters-tool-deprecated) in Search Console in April 2022. Canonical tags, consistent internal links, and robots rules are now the controls. ### Keep server response fast A server that answers in 2 seconds gets fewer pages crawled per session than one that answers in 200 milliseconds. Monitor response time for crawler user agents specifically. Crawlers visit around the clock, so a slowdown at peak hours affects them too. ## Engineer for Core Web Vitals Core Web Vitals measure user experience with three metrics: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). INP [replaced First Input Delay](https://web.dev/blog/inp-cwv-march-12) as the responsiveness metric in March 2024. The metrics are a ranking signal, and poor performance loses users whatever your rank. | Metric | Measures | Good | Poor | |---|---|---|---| | LCP | Time until the largest visible element renders | 2.5 seconds or less | More than 4 seconds | | INP | Delay between a user interaction and the next visual update, across the visit | 200 milliseconds or less | More than 500 milliseconds | | CLS | Unexpected layout movement during the visit | 0.1 or less | More than 0.25 | Improve LCP in four ways. Cut server response time with caching layers and efficient backend code. Preload critical assets. Move content generation from the browser to the server. Serve images in WebP or AVIF at the correct size. Improve INP in four ways. Split code and lazy-load scripts that are not critical. Break long tasks over 50 milliseconds into smaller pieces so the main thread can respond. Move heavy computation to web workers. Audit third-party scripts and remove or defer the tracking tags you do not need. Improve CLS in four ways. Set explicit dimensions on images and embeds so the browser reserves space. Self-host fonts and use `font-display: swap`. Do not insert dynamic content above existing content. Limit animations to `transform` and `opacity`. Measure with real users. Real user monitoring (RUM) through Google Analytics 4, SpeedCurve, or Sentry captures experience across real devices, networks, and regions. Lab tools such as Lighthouse and WebPageTest find problems. RUM confirms that a fix helped real users. Enforce performance budgets in CI. Set limits, for example total JavaScript under 300 KB and a hero image under 150 KB. Keep total page weight under 2 MB. Fail any build that exceeds a budget. Budgets stop the slow regression that comes as features accumulate. [Core Web Vitals engineering](/articles/core-web-vitals-engineering) goes deeper on each metric. ### Decide between performance work and features Base the priority on where you stand. The site can fail the thresholds, with LCP over 4 seconds, INP over 500 milliseconds, or CLS over 0.25. In that case, fix performance before new features. Poor performance undermines anything built on it. If the site is in the middle band, improve performance alongside feature work. If the site passes, keep budgets in place to prevent regression and prioritize features. ## Implement structured data at scale Schema.org structured data helps search engines understand a page and can make it eligible for rich results such as review stars, breadcrumbs, and product details. Google changes which types earn rich results. For example, since August 2023 it shows [FAQ rich results only for well-known government and health sites](https://developers.google.com/search/blog/2023/08/howto-faq-changes). Use JSON-LD. A JSON-LD block in the page holds the data separately from the visible HTML. That separation simplifies testing, keeps markup errors from breaking the layout, and lets templates manage the schema centrally. Validate before deployment. Google ignores malformed structured data. Neither the Rich Results Test nor the Schema Markup Validator offers an official API for CI. Run a schema linter or JSON Schema check in the pipeline instead. Spot-check each template with the Rich Results Test before release. Generate schema from the source data. Hard-coded values go stale when prices change, stock moves, or content updates. Build schema generation into the CMS templates or the API response layer so the markup always matches current data. Start with the foundations. Put `Organization` markup on the homepage with the brand name, logo, contact details, and social profiles. Add `WebSite` markup for the site name. Google [retired the sitelinks search box](https://developers.google.com/search/blog/2024/10/sitelinks-search-box) in November 2024, so search box markup no longer changes results. Add `BreadcrumbList` markup to show hierarchy. Monitor eligibility in the Search Console enhancement reports. They show which pages qualify and which have errors. Track rich result impressions and clicks to measure the effect. [Structured data with JSON-LD for developers](/articles/structured-data-jsonld-developers) has implementation patterns. ## Handle JavaScript frameworks correctly Tune hydration. In SSR frameworks such as Next.js, the server sends HTML and JavaScript then "hydrates" it to add interactivity. Slow hydration hurts INP, because the page looks ready but does not respond. Keep bundles small and use progressive or partial hydration that prioritizes visible elements. Use History API routing. `example.com/products/widget` is indexable. `example.com/#/products/widget` is not. Most modern frameworks default to History API routing, but verify the configuration. Give each route its own URL. People can then bookmark and share it, and search engines can index it. Render key content early. Show skeleton screens during data fetches, not blank pages. Make sure headings and primary text render quickly, even if interactive features take longer. Lazy-load only below the fold. Lazy-load images and content below the first viewport with the Intersection Observer API. Never lazy-load content in the initial viewport, because it delays LCP. Treat prerendering as a fallback. Services such as Prerender.io detect crawler user agents and serve them fully rendered HTML from a headless browser. Google now describes this [dynamic rendering as a workaround](https://developers.google.com/search/docs/crawling-indexing/javascript/dynamic-rendering), not a long-term solution. It adds infrastructure and cost. Use it only when a move to SSR is not possible. ## Give SEO a fixed place in the engineering process Bring SEO into planning. Framework selection, URL design, and infrastructure choices all affect search. They are cheaper to get right in planning than to correct later. Invite the technical SEO lead to sprint planning and architecture reviews. Write SEO requirements as tickets with acceptance criteria. Do not leave them as "nice to haves" that never get scheduled. Treat them like security or accessibility requirements: mandatory quality standards. Acceptance criteria can include schema validation, Core Web Vitals thresholds, and crawl access. [SEO testing in a CI/CD pipeline](/articles/seo-testing-ci-cd-pipeline) shows how to automate those checks. Monitor SEO beside uptime and performance. Track organic traffic, positions for priority keywords, indexing status, and Core Web Vitals on a dashboard. Alert on sharp organic drops, deindexing, and Core Web Vitals regressions. Route critical alerts into the engineering on-call rotation. Test before production. Keep staging behind authentication so search engines never index it. Crawl it with Screaming Frog and the staging credentials. Check crawlability, canonical tags, and schema before release. Document the rules in the engineering handbook: URL standards, robots rules, canonical tag use, internal link requirements, and performance budgets. Documentation stops SEO knowledge from living only in the marketing team. ### Win engineering support Put SEO value in engineering terms. Compare the acquisition cost of organic customers with paid ones. Show the link between page speed and bounce rate in your own data. Model how technical work lowers blended acquisition cost over time. Ad spend buys traffic only as long as you pay. Frame SEO as infrastructure, not marketing overhead. Split ownership clearly. The CTO owns technical SEO architecture: site structure, rendering, and performance. Marketing owns content SEO: messaging and content strategy. Hold regular coordination so technical work supports the marketing plan and the marketing plan stays within technical constraints. ### Measure the effect of technical changes Record a baseline before each change: organic traffic, positions for priority keywords, Core Web Vitals, and crawl statistics. Measure the same metrics 30 days after deployment. Avoid content strategy changes in the same period, so the result is attributable. Compare the periods in the Search Console Performance report. ## Keep SEO infrastructure secure Enforce HTTPS. Send HTTP Strict Transport Security (HSTS) headers to block downgrade attacks. Submit the domain to the browser HSTS preload list. Remove mixed content, where HTTPS pages load HTTP resources, because browsers warn users about it. Rate-limit scrapers without blocking search engines. Aggressive scrapers consume bandwidth and server capacity. Verify legitimate crawlers by reverse DNS, not only by user agent, and throttle suspicious patterns. Cloudflare Bot Management can do this automatically without harming crawl access. Test Content Security Policy (CSP) headers. CSP blocks cross-site scripting, but a strict policy can also block analytics and search engine verification scripts. That creates blind spots in SEO monitoring, so test each policy against the scripts you need. ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```