How do you protect rankings during a website redesign?
Redesigns are the most common cause of sudden traffic loss. We crawl the old site, map every important URL to its new equivalent, set up 301 redirects, keep titles and content that already rank, and check the new site in a staging environment before launch. After launch we watch Search Console daily for a few weeks. If you are planning a new site, our website development team builds this in from the start.
Do JavaScript websites have special SEO issues?
Sites built with React, Angular or similar frameworks can hide content from search engines if everything renders in the browser. We check what Google actually sees, and recommend server-side rendering or static generation where needed, as we do on our own Next.js websites.
What is a quick technical SEO checklist?
Start with these checks before anything else:
- Search Console shows your important pages as indexed
- Only one version of the site loads (https, with or without www)
- robots.txt is not blocking important sections
- The XML sitemap lists only live, indexable pages
- Each page has a unique title and one clear H1
- Mobile pages pass Core Web Vitals in field data
- Old URLs redirect in one hop to their new versions
How do you prioritise technical issues?
We score each issue by impact on indexing and rankings, the number of important pages affected, and the effort needed to fix it. Problems that stop key pages being indexed come first, followed by speed issues on high-traffic templates, then duplicate content and internal linking. Cosmetic warnings from tools, such as minor HTML validation notes, go to the bottom. This keeps development time focused on changes that move results.
How do you know technical fixes have worked?
We validate fixes in Google Search Console, re-crawl the site to confirm errors are gone, and track Core Web Vitals field data over the following 28 days, which is the window Google uses. Indexing and ranking improvements are then measured against the baseline captured before work began.
Core Web Vitals at a glance| Metric | Measures | Good threshold |
|---|
| LCP (Largest Contentful Paint) | Loading of main content | 2.5 seconds or less |
|---|
| INP (Interaction to Next Paint) | Responsiveness to input | 200 milliseconds or less |
|---|
| CLS (Cumulative Layout Shift) | Visual stability | 0.1 or less |
|---|