03
Search engineering that starts at the crawl: a sound technical foundation, migrations that keep the rankings you have already earned, and content planned from real demand, measured in Search Console rather than promised.
Ccomputese.com › blog
Best practices for secure coding
A working checklist for input validation, secrets and dependency hygiene, written for small teams.
You want to be found for what you do, in the places you serve, by people ready to get in touch.
Sound familiar?
You are replatforming, consolidating domains or shipping a JavaScript front end, and you need the search risk engineered out: URL mapping, rendering, canonicals, hreflang and monitoring after cutover.
Sound familiar?
What you can hold the work to, in plain terms.
Crawl paths, rendering and canonical signals fixed, so search engines spend their attention on the pages that earn you business.
Old URLs mapped one to one, redirects tested before cutover and monitored after, so the equity follows the content.
Topics chosen from search demand and intent, organised into clusters that lead back to the services they support.
Search Console, server logs and field data rather than vanity dashboards: what moved, why it moved and what comes next.
Search is a pipeline. Each stage fails in its own way, and each one can be measured.
Six stages: discover (XML sitemaps, internal links), crawl (robots.txt, status codes, crawl budget), render (JavaScript, hydration, lazy content), index (canonicals, hreflang, duplicates), rank (intent, entities, E-E-A-T, page experience) and click and cite (titles, rich results and citations in AI answers). Measured with Search Console, server logs, field Core Web Vitals and citations in AI answers. Migrations use a redirect map checked before and after cutover, for example /web-development/ to /services/web-design-development/ with a 301.
The disciplines inside this service, and the detail we work to in each.
01
The crawl, render and index layers, audited with a crawler, your server logs and Search Console together.
02
The riskiest moment in a site's search life, planned and rehearsed like any other cutover.
03
Schema.org markup that makes templates eligible for rich results, validated on every release.
04
Topic clusters built from demand and intent, briefed for writers who know the subject.
05
For businesses that serve an area: profiles, citations and location pages done properly.
06
What changed and why, from sources that cannot flatter, including how often AI assistants cite you when they answer questions in your field.
A rebuild usually loses search traffic through URLs nobody mapped. Every URL gets one of four decisions, recorded before launch and checked after it.
| Decision | When | What happens to its signals | How it is checked |
|---|---|---|---|
| Keep | WhenThe URL still fits the new structure. | What happens to its signalsNothing moves. Content, title, canonical and structured data must match or improve. | How it is checkedA parity diff of old and new on staging. |
| 301 to one page | WhenThe content moved to a new address. | What happens to its signalsLinks and relevance consolidate on the new URL as it is recrawled. | How it is checkedOne hop, straight to a page that returns 200, never a chain. |
| 301 merge | WhenTwo thin or competing pages become one stronger page. | What happens to its signalsSignals consolidate on the surviving URL, ending the cannibalisation. | How it is checkedThe merged page answers both searches it replaces. |
| 410 Gone | WhenThe content has no successor worth sending anyone to. | What happens to its signalsCrawlers are told the removal is deliberate, and the URL leaves the index. | How it is checkedInternal links to it are removed before launch. |
This site's own move off WordPress follows the same rules: blog URLs unchanged, and every other change a recorded decision.
Every stage ends with a document you keep and a gate you can check.
What blocks search engines, and what your customers actually search for.
Exit gate: Issues ranked by impact and effort, and the order agreed with you.
You receivePrioritized issue list
Technical and on-page changes shipped, then verified in the index.
Exit gate: Each change confirmed in the rendered HTML and in Search Console.
You receiveChanges live and verified
Content that answers the questions you should rank for next.
Exit gate: Every brief maps to one search intent and one page.
You receiveContent plan and briefs
Movement tracked against the baseline, and the plan adjusted.
Exit gate: Results read against the baseline, with dates and sources, and the next priorities agreed.
You receiveReport and next priorities
Written down before work starts, so nothing is assumed.
The public frameworks we measure the work against, and the platforms we run it on.
Client cases name the industry and the stack, never the client.
Minute Notary is a notary office in Ottawa. We designed, built and run the platform behind it: booking and payment, secure documents, a workspace for notaries, and seals anyone can verify online.
A fixed, small first engagement, then the model that fits the rest.
A first engagement
A crawl of the whole site, a read of Search Console and, where you have them, your server logs.
Fixed price
Defined projects: a website, an assessment, a migration stage
One price for that scope
Time and materials
Ongoing improvement, support and discovery work
Billed for the time used
Technical fixes can show within weeks. Content usually takes months to rank. Anyone who promises a date for a ranking is guessing.
It can, when URLs change without a plan. With a redirect map, checks on staging and monitoring after launch, the risk is managed rather than hoped away.
We earn them, with content worth citing and digital PR where it fits. We do not buy links or use networks that break search engine guidelines.
AI answers draw on the same foundations: crawlable pages, clear entities, structured data and content that states facts plainly. We track where you are cited in AI answers alongside classic rankings.
We fix them. Because we also build websites, changes ship as pull requests or CMS edits and are checked in the index afterwards. If your own developers prefer to make them, findings arrive as tickets they can act on, ranked by impact and effort.
Plain-language articles on seo, with their sources.
SEO15 min read
Optimize YouTube videos with accurate titles, descriptions, thumbnails and chapters, earn watch time, and give Google a watch page with VideoObject markup.
Updated
SEO15 min read
Google does not penalize content for being AI-generated; it acts on low-value pages made at scale to rank. What its rules say, and a workflow within them.
Updated
SEO20 min read
Practical SEO tips for websites, ordered by impact: indexing first, then titles, content, Core Web Vitals and structured data, each with a way to check it.
Updated
SEO15 min read
AI Overviews and AI Mode link indexed pages that can show a snippet. How Google picks those sources, and the controls that decide whether your pages appear.
Updated
SEO17 min read
Improve SEO as a loop: record a baseline in Search Console, audit the site, rank fixes by impact and effort, fix templates, then measure over weeks.
Updated
The same engineers answer for each of these.
Tell us what you run and what is getting in the way. You get a reply within 24 hours.
