SEO and organic growth / On-page and technical SEO
Make every important page clear to search engines and homeowners
Technical SEO is not invisible wizardry. It is the practical work that helps the right pages load, render, get crawled, get indexed, match search intent, and move a homeowner toward a useful next step. I fix the foundation without turning the report into a list of tools and acronyms.
1 job per pageA core page should have one primary search intent, one clear hierarchy, supporting proof, and one logical conversion path.
The hard truth
Good remodeling work can still be invisible, unclear, or hard to choose
Indexation
Good pages are hard to discover.
Broken links, redirect chains, accidental noindex rules, duplicate URLs, or confused architecture keep important content out of the path.
Intent
Several pages compete for the same query.
Blog posts, service pages, and location pages overlap until search engines cannot tell which one deserves the result.
Experience
The page loads late and shifts around.
Heavy images, scripts, fonts, and unstable layout make mobile visitors wait or tap the wrong element.
Technical health matters because it protects the page experience and the path into a real inquiry.
What the system needs
The foundation I inspect and improve
I connect crawl evidence with a hands-on page review. A tool can report a title length or speed metric; it cannot decide whether the page answers a homeowner’s question, proves the service, and deserves to rank.
- Crawl and indexation: robots, sitemaps, canonicals, status codes, redirects, duplicate URLs, orphan pages, pagination, and important page discovery.
- Architecture: navigation, service hierarchy, local structure, internal links, breadcrumbs, URL patterns, and page ownership of each intent.
- On-page signals: titles, descriptions, headings, copy, images, alt text, schema, entities, FAQs, local proof, and related pages.
- Performance: image size, scripts, fonts, caching, layout stability, responsive behavior, interaction delay, and hosting constraints.
- Conversion and access: readable mobile layouts, keyboard paths, labels, contrast, calls, forms, analytics, and confirmation states.
How the work moves
Fix the highest-leverage technical work first
A perfect score is not the objective. I prioritize breakage, money pages, mobile friction, duplicated intent, and issues that scale across templates before polishing isolated warnings with little business effect.
Crawl and sample
Inspect the full site, then manually review representative home, service, location, project, resource, form, and error pages.
Trace intent
Map important queries to pages, identify overlap and gaps, inspect internal links, and decide which page should own each topic.
Repair
Implement redirects, canonicals, titles, headings, schema, links, media improvements, template fixes, and performance work in dependency order.
Validate
Re-crawl, test phones and keyboards, inspect rendering, confirm analytics and forms, monitor indexing, and compare behavior after release.
Real proof, useful context, and a clear next step beat decorative marketing.
Here is the pattern I keep seeing: the site has an “SEO problem,” but the kitchen page opens with a slider, three slogans, and no clear kitchen heading until halfway down. Technical and on-page work meet on the same screen.
The business outcome
Clean structure makes every later page more valuable
When templates, architecture, internal links, and intent are clear, new project stories and resources enter a stronger system. Search engines can discover them, visitors can navigate them, and the team does not repeat the same fixes on every page.
I document what changed and why, not just the final score. That gives developers and editors rules they can carry forward: image dimensions, title patterns, heading order, schema ownership, link behavior, redirect handling, and the acceptance checks for a new page.
Release check: Technical changes are verified on the rendered page, not only in source or a crawler. I check the title and heading a homeowner sees, the phone tap, the form response, the image crop, the keyboard path, the canonical, the redirect, and the analytics event. A change is complete when the real experience and the search signal agree.
Keep building the system: Strategy and audits · Website development
Questions remodelers ask
Straight answers before you invest
Do Core Web Vitals affect rankings?
They are one signal among many and a useful measure of user experience. I improve them where the work also makes the page faster, steadier, and easier to use.
Should every page have schema?
Use schema that accurately describes visible content and supported entities. More markup is not automatically better, and unsupported claims create risk.
Can a redesign hurt SEO?
Yes, especially when URLs, content, internal links, metadata, or rendering change without a migration plan. Baselines, redirects, validation, and monitoring reduce that risk.
Is the site helping the right page win?
Call me, or book a 30-minute technical review. I will show you the first structural, speed, or intent issue I would fix.