Your team can make updates, hassle-free

Question

Answer 1

One of six promises

Your team can make updates, hassle-free

Whoever runs your office should be able to update details, change hours or prices, or post a new service without calling anyone, and without breaking the website layout.

The website that nobody can update is the website that goes stale, and stale reads as untrustworthy. Usually it’s not that your team can’t; it’s that the site was built so that any change risks breaking it, so nobody dares.

How I build it so your team can run it

Fields, not a blank canvas. The things you change often, words, prices, hours, locations, photos, team members, are simple labelled fields. The layout isn’t something you can drag out of shape, because the layout isn’t yours to drag.

Locations as a form. Opening a new branch means filling in its details. The page, the map alignment and the structure that gets it found are built automatically.

Services and specials the same way. Add one, it appears everywhere it should, formatted correctly.

Documentation and a walkthrough at launch, written for the person who’ll actually do it.

What stays with me

The things that should never change by accident: the structure, the speed, the parts that keep you found. You change content; the site keeps working.

Why this matters more than it sounds

A site your team can run is a site that stays current, which is half of trust and half of being found. It also means your website stops being a line in someone’s inbox marked “ask the developer”.

More than one location

At several locations this is where the model earns its keep: the next location is an afternoon for your office manager, not a project and not a phone call to me.

Questions people ask me about this

What is on-page SEO, and what isn’t it? On-page SEO is everything you control when you edit a page: what it's about, how it's titled, how the headings are arranged, what the words say, how images are described and what it links to. It isn't link building, speed tuning or server settings. It's the editorial work, and it's the part that quietly decides whether a good site stays findable. What can we control as website admins, and what can’t we? You control the words, titles, headings, images, links and which pages exist. You don't control how fast the site loads, how it's coded, whether the server is healthy or what Google decides this month. Work the first list; when something in the second looks wrong, tell whoever looks after the site rather than fixing it from the editor. How does a search engine interpret a web page? It reads the page as a structured document, not a picture. The title says what the page is. The main heading confirms it. The sub-headings outline the sections. The first paragraph under each heading carries the most weight. Links show what the page relates to. Images are understood through their filename and description, not their pixels. What does “one page, one topic” mean, and what is search intent? Each page should answer one thing someone is looking for. Search intent is what that someone actually wants when they type: a price, a how-to, a company to call, a definition. A page that tries to serve three intents serves none; a page that serves one, completely, is the page that gets found for it. What makes a good page address (URL)? Short, readable, and describing the page: /furnace-repair/ not /services/page-id-4471/ or /our-amazing-heating-solutions-for-your-home/. Lowercase, words separated by hyphens, no dates on pages that aren't news, and never changed once published unless someone sets up a redirect. The address is a promise about what's there. How should the content on a page be organised? Answer first, then detail. The main heading names the topic. The first paragraph gives the complete short answer. Sections follow, each with a heading that says what it covers and a first sentence that answers it. Specifics before generalities, the thing people came for before the thing you want to say, and a clear next step at the end. H1 vs H2 vs H3: what are the actual rules? One H1 per page: the title of the page. H2s for the main sections. H3s for sub-sections inside an H2. Never skip a level, never pick a heading for its size, and never use a heading for text that isn't the title of a section. That's the whole rulebook. Everything else you've read is a myth or a style preference. How do we write clear, useful headings? Make each heading say what the section answers, in the words a reader would use. "What the monthly fee covers" beats "Pricing". "How fast we respond to emergencies" beats "Service". A good test: read only the headings. If they read like a table of contents a stranger could use, they're right. If they read like a list of slogans, rewrite them. How do we write page titles (title tags) properly? The title tag is the text in the browser tab and the blue link in Google. Say what the page is, add the place if it's local, add your name at the end, and keep the whole thing under about sixty characters: "Furnace Repair in Barrie | Smith Mechanical". One title per page, each different, each honest about what's behind it. Meta descriptions: what matters and what doesn’t? The description doesn't affect ranking, so stop treating it as one. It's the two lines under your link in a search result, and it affects whether someone clicks. Write it as the honest summary of the page in about 150 characters, with the specific thing that would make the right person choose you. Google rewrites it often; write it well anyway. Why does Google rewrite my titles, and when should I leave them alone? Google rewrites a title when yours doesn't describe the page well for the query: too long, repeated across pages, stuffed with keywords, or just a company name. If it's swapping in your H1 or a cleaner version of your own title, leave it. If it's showing something wrong or off-brand, fix the underlying problem, not the symptom. How long should a page be? The honest answer. As long as it takes to answer the question the page exists for, and not a sentence more. There is no magic word count. A location page might need 300 words; a guide to choosing a furnace might need 1,500. Padding to hit a number hurts, because readers and engines both reward pages that get to the point. How do we cover a topic thoroughly without padding? Thorough means answering every question a real customer has about the topic, not adding words. List the questions people actually ask, answer each in a section, cut anything that isn't an answer to one of them. A thorough page is often shorter than a padded one, because every sentence is doing a job. How do we update existing content safely? Change the words, keep everything else. Fix what's wrong, add what's missing, update dates and prices, and leave the address, title, headings and structure alone unless they're the problem. A page that ranks has earned something; editing it is fine, rebuilding it throws that away. Note what you changed and when, so you can tell what helped. Image filenames and alt text: what are the simple rules? Name the file for what's in it before uploading: furnace-installation-barrie.jpg, not IMG_4471.jpg. Write alt text that describes the image to someone who can't see it, in one plain sentence. Leave alt text empty only for pure decoration. That's it. Alt text is for people first; search engines read it second. When do images help SEO, and when don’t they? Images help when they show something a reader wants to see: your actual work, your actual team, your actual premises, a diagram that explains. They don't help when they're stock photos, decoration, or text turned into a picture. A real photo of a real job builds trust and can bring image-search visits; a stock handshake does neither and slows the page down. What do internal links actually do? Three things. They let people get from one page to the next thing they want. They tell search engines which pages exist and how they relate, so a page with no links pointing at it is nearly invisible. And they pass importance: pages linked from many places, especially the homepage, are read as mattering more. Every page needs a way in and a way on. How do we add internal links naturally? Link where the reader would want to go next. When a page mentions a service, place or topic you have a page for, link that mention. Two to five in-content links on a typical page, one per destination, placed where the thought occurs rather than bolted on at the end. If a link wouldn't help a reader, it won't help the engine either. Anchor text: what should a link say? The words you link should describe where the link goes. "septic pumping in Orillia" tells the reader and the engine what's on the other end; "click here" and "read more" tell them nothing. Use the destination's topic in natural wording, vary it slightly across pages, and never link a whole paragraph or a bare address. Navigation links vs in-content links: what’s the difference? Menu and footer links appear on every page, so engines treat them as structure: they say which pages are the site's main ones. In-content links appear where the topic comes up, so they're read as meaning: they say what pages are about and how they relate. You need both. A page in the menu but never mentioned in content is a sign, not a destination.