Landing pages and technical SEO for Shoreditch startups
You do not need SEO explained to you. Somebody on your team already knows what Core Web Vitals are, has read the docs, and could write the ticket. The problem is that the ticket has been in the backlog since March, the campaign page for next month's launch is not started, and the two engineers who could do it are shipping the actual product. That is a capacity problem wearing a marketing problem's clothes.
I am a second pair of hands that does not need onboarding, does not need the concepts explained, and ships in days rather than sprints. A BS in Software Engineering, five years in WordPress, and the ability to read a Lighthouse trace and tell you which of those warnings actually matters for your revenue rather than fixing all forty.
In person across London. Anywhere in the UK on request. Remote worldwide.
What businesses here usually need
The work is scoped, nobody has capacity
There is a document. It is correct. It has been correct for five months. Marketing site work always loses to product work in a sprint planning meeting, and it should, which is exactly why it never gets done in house. Somebody outside the sprint who does only this is usually cheaper than the argument about prioritising it.
Forty Lighthouse warnings, no priority order
Lighthouse tells you everything and ranks nothing by business impact. Most of those warnings are noise on your particular site, two or three of them are the reason mobile LCP is four seconds, and knowing which is which comes from having profiled real sites rather than from reading the scoring rubric. Field data over lab scores, always.
Campaign pages needed on campaign timelines
A launch, a conference, a funding announcement, a paid test that needs its own page. These have dates attached and cannot wait for the next release cycle. What you need is somebody who can take a Figma file or a rough brief on Monday and hand back a live, tracked, fast page well inside the fortnight.
Landing pages and Core Web Vitals
These lead here because they are the two things you cannot easily buy inside your own sprint. Landing pages run on a one to two week timeline with two rounds of revisions, built lean, with the form and the tracking wired in before handover rather than as a follow-up ticket. If you have a design, I build to it. If you do not, I will build something plain and fast and you can put your own design over it later.
On the technical side, I profile what is actually slow rather than working down the Lighthouse list, which usually means render-blocking assets, unoptimised images, font loading, and two plugins nobody remembers installing. You get the fixes applied and a short note explaining what moved and what I deliberately left alone, so your engineers can see the reasoning rather than a score.
Execution at scale, evidenced
Wimbledon Solicitors. One person, a hundred pages, live, and still managed. The relevant part for you is not the sector, it is that the volume was delivered and the information architecture holds up. If you are wondering whether a solo consultant can absorb a large piece of work without it stalling, that is the answer.
Every rebuild I do crawls the existing site first, maps a redirect for every URL, preserves metadata, and monitors Search Console daily through the switch. If you are replatforming a marketing site off something old, this is the step that decides whether organic traffic survives, and it is the step most teams discover they skipped a fortnight later.
Speed work is judged on real-user data rather than a lab score on my laptop, because a green Lighthouse run on fibre proves very little about a phone on 4G. You get before and after from field data, and an honest note when a metric cannot be fixed without a change your team has to make.
What else I can take off your hands
In the order that usually makes sense for a Shoreditch business, rather than the order that suits me.
Usually the marketing site rather than the product: a site your marketing team can edit without filing a ticket, which is the actual requirement behind most of these conversations. Built lean, minimal plugins, clean markup. Custom Build covers replatforming with full redirect mapping, which matters if the current site has accumulated real organic traffic.
If you would rather not have WordPress in the stack at all, this is the version you already know how to review: hand-coded Next.js, deployed to your own Vercel account, repository on your GitHub. It costs more than the WordPress route and it is the right answer when the marketing site needs to be as fast as the product.
A retainer makes sense once the technical foundation is fixed, not before, because ongoing content work on a slow, badly structured site is money spent against a handicap. On the Scale tier technical fixes are included alongside content, which is the shape that tends to suit a company with an existing site and an existing audience. Local pillar work is largely irrelevant to you and I would not bill you for it.
Most likely you already have someone on paid, or you are running it in house and doing it competently. Where I am useful is the page the ads point at, because a well-targeted campaign sending traffic to a four-second page is buying attention and then discarding it. If you do want the campaigns run too, the Scale tier includes a landing page built for the campaign.
What it costs
Every price is a starting point, and every service page has the full tiers. No contracts. Cancel any time.
Asked in Shoreditch
Can you work to our Figma file and our existing component patterns?
Yes, and that is usually the cleanest arrangement. You keep design ownership, I build to the file and match the patterns already in use so the page does not look bolted on. Where a design will cost real performance, a hero video, a heavy font stack, an animation library for one transition, I will flag the trade-off with numbers rather than quietly changing it or quietly shipping something slow.
How fast is fast? We have a launch date.
A single landing page runs one to two weeks with two rounds of revisions, and the clock starts when the content lands rather than when the contract is signed. Feedback within five working days keeps it on track. A focused speed pass on an existing page is usually days. If your date is tighter than that, tell me the date first and I will say yes or no rather than say yes and then negotiate.
Our engineers will want to review anything that touches the site. Is that a problem?
It is preferable. I would rather ship through review than around it. You get a description of what changed and why, in terms that make sense to an engineer, including what I chose not to touch. If your team disagrees with a decision, they will have the reasoning in front of them rather than a diff with no context.
We are replatforming the marketing site. What actually breaks?
Organic traffic, and it breaks quietly about a fortnight after launch when nobody is watching Search Console. The causes are almost always unmapped URLs, lost metadata, and a staging environment that shipped with noindex still set. The fix is a full crawl before the move, a redirect for every URL, metadata carried across, and daily monitoring through the switch. It is not complicated, it is just boring enough that it gets dropped under launch pressure.