
Westfield Roofer
A Westfield, Indiana roofing website that pairs call and inspection routes with five before-and-after project comparisons.
FREE WEBSITE AUDITOR · SEO, AEO & GEO
A free website audit for SEO, answer readiness, and the details that make a page easier to use. Inspect the checks, choose your next fixes, and keep the report.
This free auditor comes from Trojan Digital Marketing, an Indianapolis agency that works with businesses across central Indiana and the United States.
01 / CHOOSE YOUR SCOPE
MAKE THE REPORT USEFUL
It is an automated inspection of the returned public HTML and a bounded set of related documents. A complete audit also needs search data, business context, manual content review, browser testing, and access to the systems involved.
A pass means the stated check passed in the response that was inspected. Search engine indexing, rankings, and AI citations depend on additional systems and signals this tool does not establish.
HTML response size and markup attributes are observable here. They are not mobile load time or Core Web Vitals. Use browser performance testing and real user field data to investigate those separately.
A page can be unavailable to this request, outside the link sample, disallowed by crawl rules, or excluded by the time and page limits. Open the scope and failure details. You can also audit a specific public page in single page mode.
A finding identifies an observation or a review question. Traffic impact is not measured by this report. Prioritize issues alongside query demand, existing search activity, customer needs, and the effort required to make a sound change.
A PRACTICAL FIELD GUIDE
This free website auditor examines fetched HTML from a public URL and can inspect up to five pages on the same origin. Review technical SEO signals, page structure and information available in the returned source. Findings include evidence and check states so you can distinguish detected issues, unavailable checks and questions needing human review. Use the report to decide what to investigate and how to verify a correction.
Inspect a landing page before sending people from a campaign. Review its returned title, description, headings and available indexing signals. Then check the page visually and test the form separately. A source audit and a working customer journey are related but different checks.
Export the exact URL, observation and requested correction. A developer can work from a detected directive or missing element more effectively than a vague request to improve an SEO score.
The optional sample can reveal differences between the landing page and a few linked pages. It is useful for spotting inconsistent metadata or structures worth investigating. It is a bounded sample, so it cannot establish that every page on the website behaves the same way.
Start with the page a customer would actually visit. Use the full website URL and choose whether to inspect only that page or a limited same origin sample. Avoid treating the homepage as evidence for every service, tool or location page.
Read the reported URL, checked time, request outcomes and number of pages inspected. If a page could not be fetched, keep that result separate from an inspected page. A request failure is not proof that the page is missing for every visitor.
Open the observation before deciding on a fix. Review the detected tag, heading, link or response detail. Some findings describe source facts; others are prompts to assess relevance or completeness. Neither a word count nor a heading count establishes content quality by itself.
Investigate issues that could prevent access, misrepresent the destination or obscure the next action. Then review metadata and content clarity in context. For SEO, AEO and GEO work, accurate visible business information matters more than adding unsupported claims to satisfy a checklist.
Download the report and retain the baseline. After a correction, run another audit of the same URL and compare saved results with matching scope. Use observed changes to confirm the fix; measure search performance separately after enough time and comparable data are available.
FROM INPUT TO DECISION
Illustrative audit observations. These are teaching examples, not results from your website or a claim about Trojan rankings.
| Observation | What it establishes | Useful next action |
|---|---|---|
| Returned HTML contains a noindex directive | That directive was present in the fetched source | Confirm whether the public page is intended for indexing |
| An image has an empty alt attribute | The fetched markup contains empty alternative text | Decide whether the image is decorative or needs a description |
| A linked page could not be inspected | The audit did not obtain usable evidence for that page | Open it separately and investigate the request outcome |
Keep the observation narrower than the conclusion. An empty alt attribute can be appropriate, and unavailable evidence should not be converted into a passing result or a fabricated diagnosis.
The auditor does not run a browser, execute JavaScript or perform Lighthouse testing. Review layout and interactions in a browser. Use PageSpeed Insights separately for performance evidence with its own scope.
Authorship, evidence and answers need editorial judgment. Show current services, terms and verifiable project observations. Detecting an element cannot certify expertise, content truth or selection in AI generated answers.
Yes. You can run it and keep the report without signing up or creating an account.
In this browser, when saving is on. Anyone using this browser profile may be able to open saved reports. Turn saving off to stop saving, and use Clear history to remove saved copies.
Results describe fetched HTML and a maximum five page same origin sample. They do not constitute a full site crawl, accessibility certification, security assessment or confirmation of Google indexing.
AEO and GEO observations are review prompts, not a predicted citation or ranking score. Parseable structured data does not establish rich result eligibility, and missing llms.txt is not a Google visibility failure.
No. Choose one page or a sample of up to five. The report identifies what was inspected. Larger crawls and authenticated content require a different investigation.
Browsers execute JavaScript and load resources; this auditor examines fetched HTML. Compare both views when important content appears in one but not the other.
No. Search systems consider many signals outside this inspection. Google does not require special AI markup or guarantee inclusion from completing a technical checklist.
Compare the same URL with similar scope and confirm the intended observation changed. That demonstrates a source change, not improved speed, conversions or search traffic.
Bring the report and the page that matters to your business. Trojan can review the evidence, clarify the customer journey and scope the work needed to improve the website.
Based in Indianapolis, we serve businesses across central Indiana, including Carmel, Fishers, Zionsville, Westfield, Noblesville, Greenwood, Avon and Plainfield, and clients across the United States.
Review my audit findings