Technical SEO,
fixed in your code.

We find what stops search engines crawling, rendering and indexing your pages, fix it in code and check the result live.

One URL, from symptom to proof.

A sample from an imagined store, not a client case. Not every missing page is a technical fault; this one was.

Sample store/desks/oak-standing-desk

Live for months. Unknown to Google.

  • URL Inspection: Google has never seen the oak desk page. 35 more desks show the same.
  • Google hasn’t left the page out; it hasn’t found it. So we start with discovery.

Six areas we check.
Each fix lands in code.

  • Crawl and render

    Real links. Content in the HTML.

  • Indexing

    Why each page is in or out.

  • Status codes

    The right code. Redirects in one hop.

  • Robots and canonicals

    Tags and sitemaps that agree.

  • Structured data

    Markup that matches the page.

  • Core Web Vitals

    LCP, INP and CLS from real visits.

Three formats.
Order the one you need.

Each format stands alone, with a fixed price for a clear scope.

  • Diagnosis

    An audit that traces each issue to its cause and orders the fixes.

  • Implementation

    We fix the code, or review your fixes, then check the live site.

  • Migration support

    A redirect map for every old URL, plus checks at launch and after.

Need keywords and content as well?

A site move,
mapped before launch.

A sample map for the same imagined store: every old URL gets an answer.

Old URLAnswerNew URL
/⁠desks​/⁠standing301Moved/⁠standing-⁠desks
/⁠desks​/⁠compact-⁠desk-⁠100301Moved/⁠desks​/⁠compact-⁠100
/⁠blog​/⁠2021​/⁠desk-⁠height-⁠guide301Moved/⁠guides​/⁠desk-⁠height
/⁠collections​/⁠summer-⁠sale-⁠2022410RemovedNo replacement
/⁠delivery-⁠and-⁠returns200Kept/⁠delivery-⁠and-⁠returns

Redirects tested in bulk on the live site

  • Before launch

    Benchmark traffic, then map old URLs.

  • Launch day

    Open the new site to search engines.

  • After launch

    Keep redirects for at least a year.

Is the code
holding search back?

Send us the site and what you see in Search Console. We will reply with questions and where we would look first.

Discuss your site

Frequently Asked Questions

  • The work that lets search engines crawl, render and index a site: status codes, redirects, canonical tags, sitemaps, JavaScript rendering, structured data and page speed. It is engineering work, so the fixes live in templates and code, and the people who find a problem should be able to change the code that causes it.

  • Technical SEO deals with how search engines reach, render and index the site. A wider SEO audit also covers keywords, content and tracking, with technical findings summarised; ongoing SEO is a monthly programme of research, pages and improvements. If you suspect the cause is in the code, start here; if you are not sure, start with the wider audit.

  • Not on its own. A fix removes a technical reason that stops Google from finding, rendering or indexing a page; Google still decides what to index and how pages rank. Not every page should be indexed, and a page that is not indexed is not always a fault, so we establish the reason first. Structured data can make a page eligible for a rich result only when it uses a type Google currently supports, includes the required properties and follows Google’s guidelines; even then, whether a rich result appears is Google’s decision.

  • The main drivers are the number of distinct templates, the rendering setup, the data we can access, and whether implementation or migration support is part of the work. An issue in one template repeats on every page built from it, so templates matter more than page count. We agree a fixed price for a clear scope before we start.

  • We agree the timeline with the scope. It depends on the number of distinct templates, the rendering tests they need and how quickly access to Search Console, logs and code is set up. A blocker such as key pages unreachable for search engines goes to your developers as a ticket as soon as we confirm it.

  • Yes, if you want us to. Our engineers make the changes in your codebase and review each other’s code, or we write the tickets and review what your developers change. Each fix is checked on the live site. Code we deliver is covered by 30 days of bug fixes after handover, within the agreed scope, at no extra cost.

  • Yes. We check what the server sends before any JavaScript runs and what Google renders, move content that should rank to server rendering or static generation, make navigation real links with an href, and make each route return the right status code. Our own site is built with Next.js, React and TypeScript.

  • A benchmark of the pages that earn traffic and links, a redirect map with one permanent redirect from each moved URL to its replacement, checks on the new templates before launch, redirect and sitemap tests on launch day, and monitoring afterwards. Rankings can fluctuate for a while after any move as Google recrawls and reindexes the site, so no move plan can promise that traffic stays the same. We compare with the benchmark, check pages that drop for a technical cause such as a missing or wrong redirect, and fix the causes we find. For the design side, see website redesign.

Let’s build your next advantage

Tell us what you want to launch, improve or automate. Let’s discuss the scope and the next step.

Get in touch

Prefer email?

sales@cursopic.com

Cursopic

Tell us about your project

What would you like to launch, improve or automate? A few lines are enough to start.

We use what you send only to reply to you about your request. Privacy policy (opens in a new tab)

Prefer email?

sales@cursopic.com