/ Websites and systems
What does website upkeep actually need?
Start with the pages people use, the links that lead to them, and the claims those pages make. More files are not the goal.
4 min read
What should you check first?
Start where a visitor starts. Open the homepage, follow the main navigation, and use a phone-sized screen. Can someone understand what the business does, find the right product, and reach support without guessing? A page can return a successful status and still be unreadable or send someone to the wrong place.
Then check the less visible parts: the page title, its preferred canonical URL, whether search engines are allowed to crawl it, and whether the sitemap points to a real page. Check missing URLs too. A missing page should not pretend to be a successful homepage.
- Open the important pages, not only the homepage.
- Follow product, contact, and support links.
- Check forms without adding fake customer records.
- Keep a recoverable version before publishing changes.
Does every page need a new sitemap date?
No. A sitemap is a list of the canonical pages you want search engines to find. Its last-modified date should describe a significant change to that page, not the date someone requested the sitemap.
Google says it uses lastmod when the value is consistently and verifiably accurate. If reliable page dates are not available, leaving that optional field out is more honest than marking the entire site as new every day. Publishing a sitemap is a discovery hint, not a promise that a page will be indexed.
Does AI search require a separate SEO system?
For Google AI Overviews and AI Mode, Google says the usual SEO foundations still apply. There is no special schema or extra AI text file required to qualify. Important content should be available as text, easy to find through internal links, and supported by structured data that matches what a reader can see.
A short answer near the top of an article is useful because it respects the question. The rest of the page should explain the answer, its limits, and the next decision. Repeating keywords or adding machine-facing files is not a substitute for that work.
When is another blog post worth publishing?
When there is a real question to answer or a real change to explain. A product launch, a corrected support path, or a useful explanation can earn a page. A calendar reminder alone cannot make an invented update true.
Keep the distinction visible: what is live, what is being built, and what is an opinion. Link related writing so a reader can keep going. Keep old pages accurate rather than burying them under new ones.
The maintenance standard
The goal is a site that still tells the truth and still works after the launch excitement has passed. Keep the working parts, fix the broken ones, and publish changes you can check. Compression, clean metadata, and a valid sitemap matter. So does the sentence that tells someone exactly what happens when they click.
Technical references: Google Search Central, Build and submit a sitemap; and AI features and your website. These explain discovery requirements, not guaranteed rankings or traffic.
Building something this applies to?
We take on a small number of outside builds each year — websites, apps, automations, and internal systems. Or look at what we build and operate.
Start a project