Colquhoun.AI
← All guides

Practical website research

Read a Website’s Technology Signals Without Guessing Its Whole Stack

· Colquhoun.shop editorial

Knowing that a website appears to use WordPress or Shopify can make a research conversation more specific. It cannot tell you every system the business runs, whether its integrations work, or why its customers buy. Colquhoun.shop’s public homepage check identifies a bounded set of technology signals. Use those signals as a starting point for a question, not as a complete inventory.

What the public check examines

The homepage check looks at public HTML and selected response headers. It recognizes patterns associated with platforms and services including Next.js, WordPress, Shopify, Webflow, Wix, Squarespace, Google Tag Manager, Google Analytics, Plausible, Vercel and Cloudflare.

For example, a recognizable WordPress asset path or Shopify asset hostname can support a platform hint. Some hosting signals come from response headers rather than page text. These are specific observations from a fetched response, not access to the website’s private infrastructure.

The scanner does not run the page’s JavaScript to observe everything that happens afterward. Nor does it sign in, inspect private dashboards or enumerate every backend service. A modern site can combine several platforms and load additional tools only after consent or interaction.

“Detected” is narrower than “confirmed operational”

Suppose the result identifies Google Analytics. The useful conclusion is that the response contained a recognized analytics-related signal. It does not establish that analytics events are being collected correctly, consent settings are valid, conversion tracking is accurate or the business has a particular audience size.

Likewise, a commerce-platform hint does not prove that checkout works. A hosting hint does not tell you the customer’s bill, performance under load or security posture. Keep those questions separate and use the appropriate authorized tests if you own the site.

A practical note might read: “Homepage response contains a Shopify-related asset reference. Confirm the commerce platform with the site owner before planning an integration.” That is more defensible than declaring the business’s entire architecture from a badge.

Missing is not the same as absent

The detector checks a finite collection of signatures. A service may be hidden behind a custom hostname, rendered later, used only on another page or simply absent from the detector’s current list. A result with no technology labels does not mean the website uses no tools.

Avoid using an empty result to tell a prospect that they lack analytics or need a new platform. Instead, say that the public homepage check did not identify a supported signature. If the answer matters, ask the site owner or inspect their authorized administrative tools.

Keep imported lists separate

The dashboard’s Technology view distinguishes detected information from an imported or demo technology list. A list in an imported dataset is information supplied with that dataset; it is not independently verified by the homepage check. Demo entries are fictional examples.

When preparing a research summary, label the source beside each observation. Do not merge a demo technology name into a live site assessment, and do not treat a user-imported list as fresh detection merely because it appears in the same interface.

Turn a hint into a useful next step

For your own website, a platform hint can help you route a question to the right developer. For a competitor review, it can suggest a topic to investigate publicly, such as whether the checkout experience or content structure differs from yours. It cannot establish that the platform causes better traffic, rankings or conversions.

Record the domain, time of the check, visible result and the decision you are trying to make. Then add the verification needed before acting. If the next step involves private account access, get the owner’s authorization rather than trying to infer credentials or hidden services.

Use the Colquhoun.shop dashboard for the public check and the prioritized homepage-fix guide to separate observations from actions. A small, well-qualified finding is more useful than an impressive-looking stack diagram filled with assumptions.

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.