Home Services Website Development
A seven-service home maintenance company in Oakville. Another team designed and built the site — I develop it now. The first thing I found was a menu that search engines could not follow.
Short answer
Every Season is a home services company in Oakville covering window cleaning, lawn mowing, landscaping, gutter work, moving, snow removal and property cleaning. The site is a statically exported Next.js application on Cloudflare Pages. I did not design or build it — an earlier team did. My work is what came after: making the navigation crawlable, adding a blog, and shipping ongoing changes. If your site is in the same position, that service is website maintenance & support.
The Problem Nobody Could See
The site looked finished. Seven service pages, real photography, a working quote form, clean design. A visitor could reach every page from the menu without a single thing going wrong.
But the menu was built from <button> elements calling router.push() instead of links. That works perfectly for a person — and it is invisible to a crawler, because there is no <a href> to follow. Nine of the navigation's destinations were reachable only that way.
The practical effect: Google could see the homepage, and had almost no signposted route to the seven service pages that were supposed to earn the rankings. All the effort that went into those pages was sitting behind a door search engines could not open.
What the site needed
- Navigation a crawler can actually follow
- A reason for Google to return — fresh, useful content
- Internal links pointing at the pages that make money
- Changes shipped without touching the original design
Seven Services, One Season at a Time
The business sells different work in different months — gutters and landscaping in autumn, snow removal in winter, windows and lawns in spring. The site has to carry all seven year-round while pushing whatever is in season, which is exactly what a blog is good at: seasonal content that keeps a small service site alive between busy periods.
What I Did and What I Didn't
The honest version of a shared project, written out. It costs nothing to be specific, and it removes any argument later.
Not mine
Done before I had anything to do with this site.
- Original visual design and brand
- The Next.js application and its architecture
- The seven service pages and their copy
- Photography and testimonials
Mine
Shipped to the live site, and checkable on it.
- Real crawlable links in the nav and a new footer nav
- The blog section and its publishing pipeline
- Automated seasonal article drafts for review
- Ongoing development on the live codebase
Why a working website can still be invisible
This is the failure mode nobody catches, because nothing about it looks like a failure. The site loads fast, the menu opens, every page is one click away, and the owner has clicked through it a hundred times without noticing anything wrong. There is no error to see. There is only an absence — of the plain HTML links that a crawler needs and a human never thinks about.
Modern frameworks make it easy to build this way by accident. A button with a click handler navigates just as smoothly as a link, and to a developer testing in a browser the two are indistinguishable. The difference only shows up in the one audience that cannot click: the crawler reading the HTML. That is why a site can be technically competent, visually finished, and still quietly earn nothing from search.
The fix is unglamorous and that is the point. No redesign, no rebuild, no new framework — just the correct element in place of the convenient one, plus a reason for search engines to come back and look again. Most of what an inherited site needs is like that: small, specific, and worth more than the rewrite somebody will inevitably suggest instead.
Questions about work like this
Why would a website have no crawlable links?+
Because a modern JavaScript framework lets you navigate without them. A menu item can be a <button> that calls router.push() — it works perfectly for a person clicking it, and a search engine sees nothing at all, because there is no anchor tag with an href for a crawler to follow. Nothing looks broken, which is exactly why it survives for years.
Can you take over a website another developer built?+
Yes, it is a normal part of what I do. What I need is repository access, the hosting account and the domain registrar login. If the stack is one I work with — Next.js, WordPress, plain PHP or static — I can usually start shipping within a few days. If there is no repository at all, that is a rebuild conversation, and I will say so rather than patch around it.
Do you claim you designed sites you only maintain?+
No. Every Season was designed and built by an earlier team, and this page says so at the top. Portfolio pages where I did the whole build say designed and built, pages where I replaced an existing site say rebuilt, and pages like this one say ongoing development. Anyone can check a repository history in ten seconds, so there is nothing to gain by blurring it.
What does ongoing development on an existing site cost?+
It is quoted per piece of work, because inherited codebases vary enormously. A small content or layout change is usually under an hour. A new section with schema and sitemap entries is a day or two. For a fixed monthly arrangement, the website maintenance and support page covers what that includes.
More on website maintenance & support · SEO optimization · Pricing
Not sure whether Google can actually read your site?
I'll check it and tell you plainly — run the free website audit, or send me the address and I'll look myself.
Explore More of My Work
From restaurants and law firms to contractors and clinics — see how I help businesses grow online.
View All ProjectsWeb Design Across Toronto & the GTA
I build websites for clients across Canada and beyond — but I'm based in Toronto. For a planning session or on-site business photos, I'll come to you. Pick your city: