Colquhoun.AI
← All guides

Practical website maintenance

Turn a Homepage Check into a Prioritized Fix List

· Colquhoun.shop editorial

A website check is useful when it helps you decide what to do next. A row of green checks is not a business outcome, and a missing signal is not always a defect. Colquhoun.shop’s public homepage scan gives you a small set of observable facts you can turn into a focused maintenance list.

Know what you are checking

The built-in scan reads a public website’s homepage HTML over HTTPS. It looks for a title, meta description, canonical link, viewport declaration, first-level headings and visible technology hints. It also probes the standard root locations for robots.txt and sitemap.xml.

This is not a full crawl of every page, a security audit, a search-ranking report or a traffic measurement. It does not run the page’s JavaScript. A site that builds its content in the browser may show more to a human visitor than the scan can see in its initial HTML.

Keep the checked domain and scan timestamp with your notes. Results can be cached for up to an hour, so an immediate repeat may not represent a new fetch after you edit the website.

Separate observation from diagnosis

Start with the literal finding. “No meta description found in the fetched homepage HTML” is more accurate than “this website has bad SEO.” The first statement tells you what to inspect. The second claims more than the check establishes.

FindingUseful next check
Title presentDoes it accurately describe the page and business?
Description missingInspect the homepage source and CMS settings before adding one.
Canonical foundDoes it point to the intended public version of the page?
Viewport presentOpen the actual page on a narrow screen; presence alone does not prove a good mobile layout.
Root sitemap not foundCheck whether the site uses a different sitemap location.

A present tag can still be unhelpful. A vague title such as “Home” passes a presence check but gives visitors little context. Conversely, a missing root sitemap result does not prove that no sitemap exists anywhere on the site.

Prioritize the impact, not the color

Sort your observations into three groups: visitor problems, clarity improvements and items needing more evidence. A homepage that cannot be opened normally deserves attention before polishing a description. A confusing title may be a straightforward improvement. An unfamiliar technology hint generally calls for investigation, not an urgent migration.

Do not treat a failed scan as proof that the website is down for everyone. Automated requests may be blocked, a response may time out, or the page may return a format the scanner does not support. Open the public page normally and compare the symptoms before choosing a fix. Respect access restrictions rather than trying to get around them.

Use technology hints as clues

The scan can recognize some platform and analytics signatures in HTML or response headers. Those are visible hints, not a complete software inventory. A signature may be left behind by an old integration, and an active service may leave no recognizable signature in the fetched response.

If you are reviewing your own site, confirm a hint in your hosting dashboard or code before changing anything. If you are researching a competitor, keep the claim modest: “a visible signature suggests this technology” is better than asserting you know their entire stack.

Make the fix list small enough to finish

For each item, record the observed evidence, proposed change, owner and verification step. For example: “Homepage title is ‘Home’; replace it with an accurate product-and-brand title; verify the rendered page and source after release.” Avoid changing unrelated design, authentication or payment settings during a metadata cleanup.

After publishing a change, check both the source and the human experience. A technically present viewport tag cannot tell you whether buttons overlap on a phone. A canonical link cannot tell you whether the copy answers a customer’s question.

For deeper wording analysis, use the Web Reader and Keyword Density workflow. For income planning, keep this scan separate from traffic-based revenue scenarios. Homepage HTML alone does not reveal visits, conversions or earnings.

Return to the Colquhoun.shop dashboard with one question: which observed issue can you fix and verify next? That is the point of a useful check.

This guide describes the built-in Web Reader and Keyword Density behavior verified for this publication. Available data depends on the page response; these tools do not measure visits or search rankings.