A beautifully designed site launches to a round of applause. Then nothing. Weeks pass, traffic limps in, and by the third month it’s clear the site is more or less invisible to search engines.
The frustrating part is that this is almost never a design problem or a content problem. It’s a timing problem. Most teams treat SEO as something you bolt on after launch, when the decisions that matter most — the ones that are painful and expensive to undo — all happen before a single line of code gets written.
Build with SEO in mind from the start and you skip the bulk of the cleanup that otherwise eats three to six months after launch, along with the structural rewrites that quietly wreck a site’s ranking potential. A site planned for search from day one indexes faster, climbs higher, and holds its position more reliably than one retrofitted in a hurry. It’s the whole reason my team folds SEO and web development into one process instead of treating them as separate stages.
The three phases where SEO actually gets decided
It helps to stop thinking of SEO as a task and start seeing it as a set of decisions spread across the project.
Before development. Your semantic core (the keyword strategy) and your site architecture get locked in here. Change your mind later and the cost climbs fast — you’re not editing a page, you’re re-pouring the foundation.
During development. URL patterns get encoded, rendering gets chosen, meta tags and schema get wired up. The technical skeleton is set in this window.
Before launch. Everything gets tested and audited. A problem caught here is a quick fix; the same problem caught a month after launch is an emergency, complete with re-crawling and lost ground.
Once you see it this way, SEO stops being the thing you cram in at the end. It runs through the whole timeline.
Building the semantic core
The semantic core is just the structured answer to one question: what is this site about, and what are people typing when they need it? The process I use:
Market intelligence. Look at what competitors rank for, find the gaps they’ve left, and spot seasonal patterns. Semrush, Ahrefs, AnswerThePublic and Google Trends each show a different slice.
Collect keywords. Pull together your primary topics (5–15 core themes), the long-tail variations that reveal intent (specific three-plus-word phrases), and the question-shaped queries — “how to,” “what is,” “where to find.”
Cluster and tag by intent. Group keywords that mean the same thing, then label each cluster by what the searcher actually wants: to learn (informational), to find a site (navigational), to compare (commercial), or to buy (transactional). Intent is the step most people skip, and it’s the one that makes everything downstream easier.
Map topics to the site. Every cluster should match a real area of the site. This quietly dictates your URL structure and navigation, because it tells you which pages need to exist and how they relate.
Write it down. One reference sheet — topic pillar, primary keyword, volume, difficulty, long-tail variations, target URL, intent — shared with everyone touching the project. A semantic core that lives in one person’s head isn’t a strategy, it’s a liability.
The thing to resist is the urge to “figure out keywords later.” By the time development is underway, your architecture is already hardening around whatever assumptions you made. Do this first.
Site architecture: easy to crawl, easy to trust
Your structure decides whether search engines can reach your content efficiently, which pages build authority, and how fast new pages get indexed. A few principles worth holding firm on:
Keep the hierarchy shallow. Three to five primary categories, subcategories under those, pages under those. Aim to keep everything within three clicks of the homepage — a page three clicks deep gets crawled far more thoroughly than one buried six clicks down.
Keep URLs flat. Three levels deep, max. /resources/blog/seo-techniques is fine; /resources/guides/content/seo/techniques/best-practices is a maze.
Organize by theme. Build pillar pages that cover a topic comprehensively, then support each with cluster pages on the specifics. Interlink them deliberately — that’s how you signal you actually own a subject rather than just touching it.
Leave no page orphaned. Every page worth having should be reachable from navigation, footer, or an internal link. If nothing points to a page, search engines treat it as if it doesn’t exist.
A visual sitemap drawn before development becomes your blueprint. It’s worth the half hour.
URL structure and the technical foundation
A few URL habits that pay off forever:
• Separate words with hyphens (on-page-seo, not on_page_seo)
• Skip special characters and stray parameters
• Keep them descriptive but short — three to five words
• Mirror your site hierarchy in the path
• Decide the strategy before you build, because changing URLs later means a pile of 301 redirects and the mistakes that come with them
And the technical checklist that should be in place at launch:
robots.txt — Block what crawlers don’t need (admin, staging, internal search results) while keeping important resources open, and point to your sitemap. One thing worth deciding deliberately in 2026: how you treat AI crawlers like GPTBot, ClaudeBot, PerplexityBot and Google-Extended, since that governs whether your content can show up in AI answers.
sitemap.xml — List every page that matters, auto-generated through your CMS so it stays current.
Canonical tags — Self-referencing on unique pages, so you don’t split authority across duplicate URLs.
HTTPS — Non-negotiable. SSL, clean HTTP→HTTPS redirects, and a Strict-Transport-Security header.
Mobile — Responsive is the floor. Test on real devices: content readable without zooming, tap targets at least 48px. Over half of search traffic is mobile, so a layout that “mostly works” on a phone is a layout that mostly loses.
Core Web Vitals — These are confirmed ranking factors, and a couple of the numbers people memorized a few years ago are now wrong:
• LCP (Largest Contentful Paint): under 2.5 seconds.
• INP (Interaction to Next Paint): under 200ms. This replaced First Input Delay (FID) back in March 2024, and Chrome dropped FID support entirely — so if your checklist still says “FID under 100ms,” it’s out of date. INP is stricter too, since it watches every interaction in a session rather than just the first.
• CLS (Cumulative Layout Shift): under 0.1.
One thing developers miss: these are measured from real users (Chrome’s field data) at the 75th percentile, not from a one-off lab test. A page can look great in PageSpeed Insights’ lab run and still fail in the field. You hit the targets with image compression, leaner CSS and JS, caching, and a CDN.
Schema markup: talking to machines in their own language
Schema turns plain text into structured data that search engines — and increasingly AI models — can read without guessing. It powers rich results, featured snippets, and the answers showing up in voice and AI search.
The types worth having on most sites:
• Organization (homepage) — name, logo, contact, social profiles. The backbone of a knowledge panel.
• Article / BlogPosting (posts) — headline, publish date, author, image.
• FAQPage (high-intent pages) — question-and-answer pairs that make you eligible for snippet placement.
• BreadcrumbList (every page) — communicates hierarchy and tends to help both click-through and crawl efficiency.
Use JSON-LD — it’s clean, sits separately from your HTML, and it’s the format Google prefers. Here’s the shape of it:
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "SEO at the Development Stage",
"datePublished": "2026-06-08",
"author": { "@type": "Person", "name": "Roman Makuev" }
}
One rule trips people up: your schema must match what’s actually visible on the page. Don’t mark up an FAQ that isn’t there. Validate everything with Google’s Rich Results Test before launch.
On-page: titles, descriptions, headings, links
Your title tag is the one piece of on-page real estate that wins or loses the click before anyone reads a word, so treat it like a tiny ad. A pattern that works is keyword first, then the value, then a modifier — something like On-Page SEO Checklist: 10 Actionable Techniques [2026]. Keep it under about sixty characters, lead with the part that makes someone curious, and never reuse a title across pages. Keyword-stuffing does the opposite of what people hope.
Meta descriptions are a different job. They won’t move rankings on their own, but they decide whether the listing looks worth clicking, so write them like a one-line pitch: benefit, a quick why, a nudge to act — roughly 155–160 characters, with the main keyword sitting in there naturally.
For headings, one H1 per page carrying the primary keyword, then H2s and H3s to give the content a logical shape. Don’t skip levels (no jumping H2 → H4) — it confuses screen readers and crawlers alike.
Internal linking is the most underused tool on this list. Use the pillar-and-cluster model: a broad pillar page that owns the topic, surrounded by cluster pages that go deep on the narrow stuff, with clusters linking up to the pillar and the pillar linking back down.
Pillar: "Content Marketing Strategy: Complete Guide"
├── Cluster: "Content Marketing for SaaS"
├── Cluster: "Content Calendar Creation"
└── Cluster: "Measuring Content ROI"
That web of links tells a search engine you’ve actually covered the ground. Use anchor text that describes where the link goes (not “click here”), keep the important links high on the page, favor a handful of meaningful links over a wall of them, and point your strongest existing pages at anything new so it inherits a little authority.
Measuring what you built
Once a month is plenty. I’d watch organic traffic, the average position of your target keywords, click-through rate, how many pages are actually indexed, and your Core Web Vitals baselines. Lately it’s worth adding one more: whether the AI tools mention you at all — open ChatGPT, Gemini or Perplexity, ask the questions your customers ask, and see if you come up.
The free tools do most of the work: Search Console and Analytics 4. Add a rank tracker (Semrush, Ahrefs, Moz) and a speed tool (PageSpeed Insights or GTmetrix) so you can see the gap between lab numbers and real users.
Then run a simple monthly loop. Look at the trends, find the openings — a page with lots of impressions but few clicks usually needs a better title and description; one stuck around position eight to ten usually needs more depth; new query types showing up are a hint to build something for them. Make the change, then leave it four to six weeks before judging it, because search rarely moves on your timeline.
Timelines, roughly, by project size
None of this is a rule, but the shapes are consistent after enough projects.
• Small (10–20 pages): about 2–4 weeks. Core and architecture first, then URL strategy and templates, then building against the checklist, then a pre-launch audit.
• Mid-size (50–200 pages): about 6–8 weeks. Planning and stakeholder alignment, architecture and templates, a few weeks of active development, pre-launch prep, launch.
• Enterprise (500+ pages): 12+ weeks. Comprehensive planning and competitive analysis, tech specs, two development phases (schema lands in the second), pre-launch and migration planning, then a phased launch you actually monitor.
The non-negotiables
If you only have appetite for a few things, these get you most of the way. Get the semantic core down before development starts. Build an architecture that’s logical and shallow enough to navigate without thinking. Make the mobile experience genuinely good, tested on a real phone. Hit the current Core Web Vitals thresholds. And link internally with intent, guiding both users and crawlers through the site.
When there’s room for more: full schema coverage (Organization, BreadcrumbList and FAQ at minimum), tidy URLs and meta tags, deeper performance work, and the unglamorous habit of revisiting all of it after launch instead of declaring victory.
Common mistakes
Most failures come from the same short list: treating SEO as a post-launch task; building a URL structure six levels deep that you can’t unwind later; shipping a mobile version that “mostly works”; optimizing for FID, a metric that no longer exists; and launching with no analytics or Search Console in place, so for the first crucial weeks nobody can see anything.
Your action plan
This week. Carve out two hours: an hour on the semantic core, half an hour sketching architecture, half an hour settling the technical approach. The point is to make the expensive decisions on purpose rather than by accident.
This month. Lock down architecture and URL structure, draft your title and meta-description templates, and get Search Console, Analytics and a rank tracker set up before you need the data.
During development. Keep SEO inside the workflow, not off to the side. Work the checklist, test on a phone constantly, watch Core Web Vitals as you go.
Before launch. Run a proper audit, fix anything critical, confirm tracking is firing, validate your schema.
After launch. Watch it closely the first week, then settle into a monthly rhythm and improve in small steps. If carrying that yourself isn’t realistic, ongoing search work is exactly what an experienced SEO agency is built to handle.
Final thought
The sites that end up dominating search almost never got there by luck. They got there because someone decided, before a line of code was written, how the thing would be structured, which topics it would own, and how information would move through it. That discipline compounds — a small edge at the foundation becomes a wide gap a year later.
Your development stage is the most leverage over search visibility you’ll ever have. Plan the structure, claim your topics, and build for both the humans reading and the machines now reading on their behalf — and start before the first line of code, because everything else grows out of that.
Top comments (1)
As a Calgary web design agency, we see many businesses struggle when SEO is treated as an afterthought. Fixing issues like poor URL structures, slow site speeds, or missing metadata after launch is always more expensive and time-consuming than addressing them from the beginning. By integrating SEO into development, we ensure the foundation is solid: clean architecture, responsive design, fast performance, and content aligned with user intent. Sites built this way not only launch stronger but also start indexing faster and achieve sustainable rankings, which directly improves ROI over time.
Some comments have been hidden by the post's author - find out more