The River Bend is a UK fishing guide site I built from nothing. The domain was registered on 30 June 2026, and within 75 days the site was appearing in Google over 8,000 times a day and earning more than 100 clicks a day. This case study covers how it was built, what was done differently from a typical new site, and what the results look like.
River Bend is my own site, and it’s an affiliate site: some guides include product recommendations that earn a commission.
At a glance
| Site | theriverbend.co.uk |
| Type | New content and affiliate site, UK angling |
| Platform | WordPress |
| Work | Site build, content structure, schema, internal linking, publishing pipeline, affiliate integration |
| Impressions since launch | 244,540 |
| Clicks since launch | 2,539 |
| Daily impressions | 8,000+ within 75 days |
Figures are from Google Search Console, covering launch to 14 September 2026.
The starting position
A brand new domain starts with nothing. No history in Google, no links, no trust. The usual advice is that a new site should expect months of very little before search traffic arrives, and fishing is a crowded subject with long-established forums, magazines and retailers ranking for the obvious searches.
The aim was to prove that a new site built carefully, with search designed in from the first line of code rather than added later, could earn meaningful visibility quickly without cutting corners on quality.
The plan
Rather than publishing a few posts and waiting, the site was planned as a complete resource before launch. Content was organised into nine pillars, each with a hub page and a full dropdown menu, so every guide had a clear parent and a clear route from the homepage.
The priority was depth over volume. The guides that matter most, such as individual river guides, species profiles and explanations of the rules anglers need to know, were written to answer the question fully rather than skim it.
The SEO and AI search strategy
River Bend was planned as a search strategy first and a website second. Seven areas worked together:
| Area | The aim | What it involved |
|---|---|---|
| Site architecture | Give every guide a clear place and route from the homepage | Nine content pillars, hub pages and full dropdown menus |
| Technical build | A fast, clean site Google can crawl from day one | Lightweight WordPress set-up, mobile layouts, caching, clean URLs |
| Deep content | Answer each question better than what already ranks | River guides, species profiles, rules and gear explainers, researched and edited |
| Internal linking | No page left without links pointing to it | Related-article links, breadcrumbs, and an orphan audit after every batch |
| AI search readiness | Be quotable in AI Overviews and assistants | Direct answers at the top of every guide, visible FAQs, FAQ schema, and AI crawlers allowed |
| Monetisation | Earn from the traffic without spoiling the content | Affiliate products matched to each page’s subject |
| Measurement | See what’s working early | Search Console tracking of impressions, clicks and positions by page |
What was built
- WordPress site on a lightweight theme, with mobile layouts, caching and a speed-focused set-up
- Nine content pillars, each with a hub page and a full dropdown menu
- Schema, breadcrumbs and related-article links on every page
- A publishing pipeline that takes a finished draft, its metadata and its schema live through the WordPress API, so pages go out complete rather than being fixed up afterwards
- An orphan-page audit that runs after every batch of content, so no page goes live without links pointing to it
- Affiliate product boxes matched to each page’s topic
The whole build follows the same standards I apply to client sites: breadcrumbs and schema on every page, meta titles and descriptions written by hand, and internal linking rules that stop pages being orphaned.
How the content was written
Every guide went through the same writing system I use for client content: a brief, research into what already ranks and what it misses, an outline, a draft from a writer pass and a separate editor pass, then checks for voice, sources and structure. Each guide opens with a direct answer to the question it targets, so it can be quoted cleanly in search results and AI answers, and each one ends with a visible FAQ backed by FAQ schema.
Guides were written to a site-specific voice and set of rules, so a river guide reads like it was written by someone who knows the water, not like a template. Where a guide recommends fishing gear, the products are matched to the page’s subject rather than dropped in generically.
Why the publishing pipeline mattered
On most new sites, pages go live in a hurry and get fixed afterwards: titles tidied, schema added, links sorted out later. The publishing pipeline reverses that. Each finished guide goes live through the WordPress API with its meta title, description, schema and category already in place, so Google’s first crawl sees the finished page.
That also made it practical to publish a complete resource before launch rather than a handful of posts, which is a big part of why the site earned visibility so quickly.
The results
Since launch, River Bend has generated 244,540 impressions and 2,539 clicks from Google. Within 75 days of the domain being registered, the site was appearing in Google over 8,000 times a day and earning more than 100 clicks a day, with the best day so far bringing 128 clicks from 8,746 impressions. Average position is now on page one.
[Chart: daily clicks from Google]
[Chart: daily impressions in Google]
[Chart: average position, lower is better]
The pages doing the work
The deep guides earn the clicks, each ranking around position seven on average:
| Page | Clicks | Impressions | Avg position |
|---|---|---|---|
| River Severn fishing guide | 194 | 7,742 | 7.3 |
| River Thames fishing guide | 178 | 9,576 | 7.2 |
| River Great Ouse fishing guide | 149 | 4,067 | 6.5 |
| Fishing rod test curve explained | 147 | 10,645 | 6.6 |
| Hampshire Avon fishing guide | 87 | 1,892 | 8.7 |
What I learned
New content is orphaned by default. After one batch went live, the audit found eleven gear guides that were in neither the Gear menu nor the Gear hub page. Rebuilding that menu from three columns to four brought all 22 gear pages back into reach, and the orphan check now runs after every batch.
That’s the kind of problem that quietly holds a site back for months if nobody checks, and it’s why the internal linking and orphan checks are part of every site I build.
The pages that took off first weren’t the broad ones. Detailed guides to individual rivers, such as the Severn, the Thames and the Great Ouse, and a plain-English explainer on rod test curves led the clicks, well ahead of general beginner content. On a new site with no authority, depth on a specific subject earns trust from Google faster than breadth.
Limitations
Seventy-five days is early in a site’s life, and fishing has seasons that haven’t fully played out yet, so the figures describe a strong start rather than a finished result. River Bend is also my own site, so I control every decision in a way a client project doesn’t always allow. The figures will be updated as the site matures.
Services used
This project draws on WordPress website builds, content strategy and schema markup. It sits in the publishers and affiliate sites industry, and if you’re interested in what a well-planned build can do for a local business, the Barlows Caravan Park case study shows a very different kind of site.
FAQ
How long does it take a new website to get traffic from Google?
It varies a lot with the subject, competition and how well the site is built. River Bend, a new WordPress site in a crowded subject, was appearing in Google over 8,000 times a day within 75 days of registering the domain. A carefully planned structure, deep content and clean technical set-up made a real difference to how quickly that happened.
Does a new site need links before it can rank?
Links help, but a new site doesn’t have to wait for them to earn visibility. River Bend’s early impressions came from deep, well-structured guides answering specific questions, with clean internal linking and schema. Useful content that answers searches better than what’s already ranking can start earning impressions while authority builds.
Is WordPress good for SEO?
WordPress can be excellent for SEO when it’s set up carefully. It handles clean URLs, custom titles and descriptions, schema and fast hosting well. The problems usually come from heavy themes, too many plugins and pages published without structure or internal links, which are all things a good build avoids from the start.
Want a site that grows like this?
Whether you’re starting from scratch or rebuilding, get in touch and I’ll tell you what I’d plan first, or ask for a free assessment of your current site.