ZNELK hello@znelk.com Start a project

Capability · Technical SEO

Your site is big, complicated or changing. We make sure search can still understand it.

Migrations, indexing problems, structure that has outgrown itself, pages search cannot read. We investigate properly, explain it in plain English, then work with your engineers until it is fixed.

Start a project All expertise

Where we come in

Where people usually call us.

Migrating

You are migrating, or you already did and traffic dropped.

We plan the move before it happens: every URL mapped, redirects tested on staging, the weeks after launch watched closely. If it has already gone wrong, we work out what changed and what to fix first.

Outgrowing

Your site has outgrown its structure.

Categories, filters and templates that made sense at 5,000 pages get messy at 500,000. We rework the architecture and internal linking so that growth stops creating duplicates and dead ends.

Indexing

Pages you care about are not showing up in Google.

Or pages you do not care about are crowding them out. We find what Google crawls and skips, and why, using your server logs and not only a tool.

Traffic drop

Traffic fell and nobody can say why.

We trace it back to the change behind it: a release, a template, a rule, a setting. Then we tell you what to fix and in what order.

Rendering & AI

Your site looks great to people and empty to crawlers.

We check what Google and AI crawlers actually receive, then find the lightest fix, often without touching the design. We add structured data so answer engines have something to read and cite.

After launch

Fixes keep slipping back in with every release.

Release checks, monitoring and alerts, so the work stays done while the site keeps changing.

From the work

A few things we have actually fixed.

Duplicate pages

Large job platform

The situation

Near-identical category pages competed with each other. An acronym and its full title each had a page, and neither ranked well.

What we did

We matched pages by shared taxonomy first, then checked search demand before calling anything a duplicate, because a shared ID alone proves nothing. Then we wrote the redirect and merge tickets.

What it meant

One strong page ranks instead of two weak ones, and the decision came from demand, not from a guess.

Missing pages

Large job platform

The situation

A spike of broken pages turned out to be real searches for valid job and city combinations that the site had never created.

What we did

We traced it from the server logs, scripted an audit of which combinations deserved a page, and wrote page-generation rules by tiering cities and occupations. Nothing existing was deleted. A phased roadmap went to engineering.

What it meant

The site stopped sending visitors to dead ends, and it now has a rule for which pages deserve to exist.

Pages that expire

Large job platform

The situation

Landing pages for jobs that had expired sat empty and wasted crawl time, while pages that should have come back stayed gone.

What we did

We designed the retirement rules: when an empty page returns a 404, a separate suppressed status, and automatic recovery when jobs return. The same checks became the quality gate before expanding to more occupations and states.

What it meant

Search sees fewer empty pages, and pages come back by themselves when there is something to show.

Wasted crawling

Large job platform

The situation

Google spent its time on filter and ad-tracking variants of the same pages.

What we did

We wrote the robots and canonical rules to stop it, and in the process found one rule that was blocking real job pages.

What it meant

Crawling went to the pages that matter, and a quiet blocking mistake was removed.

From our work at a global job platform. Details are simplified and figures are left out until they are cleared for publication.

Scope

What is included.

  • Log file analysis
  • Crawl budget and crawl management
  • Indexation control and canonicals
  • JavaScript rendering and SSR
  • Site architecture and internal linking
  • Faceted navigation and parameters
  • Pagination
  • XML sitemaps for millions of URLs
  • Redirect architecture
  • Structured data and schema
  • Hreflang and international setup
  • Core Web Vitals and performance
  • Migrations
  • Monitoring and alerts
  • Release QA and technical governance

How it works

From first look to shipped fixes.

  1. 01

    Look properly

    We look at how search engines and AI crawlers crawl, render and index your site, using logs and live data as well as tools.

  2. 02

    Say what matters

    A short, ranked list of fixes by business impact and effort, written as tickets your engineers can pick up.

  3. 03

    Stay until it ships

    We stay close through release, QA and monitoring, or carry on as a growth partner.

You work directly with Marketa. Tools we work in: Botify, Splunk and ClickHouse for logs, Search Console, Screaming Frog, Ahrefs, Amplitude, Python, and Jira and Confluence for turning findings into engineering work.

Questions

Common questions

Do you work with our in-house SEO and engineering teams?

Yes, that is the usual setup. We add depth on the hardest problems and hand over tickets, specifications or working code your team can ship.

Is this only for very large sites?

No. The biggest platforms have the most complicated problems, but one stubborn issue on a smaller site deserves the same investigation.

When should we bring you in on a migration?

Before it starts, if you can. We benchmark, map redirects and test staging before launch. We also help after a migration that went wrong.

Can you build what you recommend?

Often, yes. We prototype templates and modules as working code your engineers can review and ship.

Related

Connected expertise.

Capability

SEO-First Websites

Search built into the website before the website is built.

Capability

Ongoing SEO Retainer

A senior SEO partner on call, so the work keeps moving after the plan.

Start a project

Tell us what you are working on.

A challenge, a launch, a migration or an ongoing partnership. Tell us where you are and we will say what we would look at first.

Looking for market intelligence instead? Explore ZNELK Intelligence