Proof of method
Sample Site Clarity Report
A deeper sample of how Eiway turns public website cleanup signals into a practical issue map, severity rubric, and fix-priority report.
How Eiway reads a cleanup problem
A useful website cleanup report should separate what is visible from what is only knowable with owner-approved access. Eiway starts with public signals first, then marks Search Console, GA4, WordPress admin, or hosting checks as optional access items.
Visible evidence
Public pages, navigation, footer, contact path, policy pages, sitemap, robots file, canonical signals, broken links, visible warnings, demo leftovers, and page clarity.
Access-needed evidence
Search Console coverage, GA4 engagement, plugin settings, WordPress admin state, hosting logs, payment records, and form delivery settings are reviewed only if the owner provides access later.
Fix priority
Findings are grouped by risk, effort, and sequence so the owner can fix trust and cleanup issues before chasing lower-priority polish.
Sample executive summary
The reviewed site has a real purpose and useful material, but it still creates uncertainty for a visitor or reviewer. Public checks suggest four priority areas: unfinished WordPress cleanup, weak trust-page clarity, indexing ambiguity, and content sections that need stronger original usefulness. Search Console and GA4 sections are marked optional because they require owner-approved access.
Sample scoring summary
| Review area | Sample score | What this means | First practical fix |
|---|---|---|---|
| Homepage clarity | 3 / 5 | The business purpose is visible, but the next step competes with several equal calls to action. | Make one primary path obvious, then keep secondary paths lower on the page. |
| Trust and identity | 2 / 5 | Contact and policy pages exist, but author, business, and review-process signals are light. | Clarify who maintains the site, what is reviewed, and how readers can contact the business. |
| WordPress cleanup | 2 / 5 | Old template content, plugin warnings, empty sections, or duplicate utility pages are still visible. | Remove public leftovers before adding more content. |
| Publisher value | 3 / 5 | The topic is relevant, but the best pages need more examples, checklists, and verification steps. | Deepen the strongest pages instead of publishing many thin pages. |
| Indexing readiness | Review | Public sitemap and canonical signals can be checked, but final diagnosis may require Search Console. | Confirm submitted sitemap URLs, canonical pages, and excluded URL patterns. |
Severity rubric
| Severity | Use when | Example public signal | Action timing |
|---|---|---|---|
| High | The issue can directly damage trust or block the intended journey. | Visible PHP/plugin warning, broken request path, public placeholder page, or incorrect business identity. | Fix before promotion, review, or paid traffic. |
| Medium | The issue weakens clarity or quality but does not fully block the site. | Thin trust page, vague service page, repeated guide intro, confusing internal links, or weak content examples. | Fix in the next controlled content pass. |
| Low | The issue is useful polish after higher-risk cleanup is handled. | Minor heading order, old wording, or secondary design inconsistency. | Batch with other low-risk cleanup. |
| Review | The public signal is incomplete without owner-approved data. | Indexing status, query movement, GA4 attribution, form conversion, or plugin setting behavior. | Verify with the owner before changing anything. |
Sample issue anatomy
| Visible signal | Why it matters | How to verify | Fix direction |
|---|---|---|---|
| Plugin warning appears on a public page | Visitors may question whether the site is maintained before they read the offer. | Open the page in a private browser and mobile viewport; check whether the warning appears without logging in. | Identify the plugin or theme source, fix safely, then recheck the same URL and important templates. |
| Privacy or contact page looks unfinished | Trust pages help readers and reviewers understand who is behind the site. | Open the policy/contact pages from navigation and footer, then check mobile readability and contact clarity. | Restore layout, remove placeholders, confirm contact path, and avoid asking for sensitive data too early. |
| AdSense content feels broad but not specific | General advice can look low-value if it lacks examples, decisions, or verification steps. | Ask whether a reader can take action without buying a service. | Add checklists, examples, repair criteria, source context, and a clear no-guarantee boundary. |
| Search Console status is misunderstood | Submitted, discovered, crawled, indexed, and excluded are different states. | Compare public sitemap URLs with URL inspection examples if access is available. | Map each status to the next safe check instead of changing pages blindly. |
Public checks versus optional access checks
Can be reviewed publicly
- Homepage purpose and next step.
- Navigation, footer, and internal links.
- Visible WordPress errors or template leftovers.
- Policy/contact page presence and readability.
- Sitemap, robots, canonical, noindex, and redirect signals that are publicly visible.
Needs owner-approved access
- Search Console indexing and query data.
- GA4 engagement and conversion events.
- WordPress plugin/theme settings.
- Contact form delivery logs.
- Payment, Stripe, hosting, or email account records.
How this helps before buying anything
You can use this sample to audit your own site at a high level. Look for public warnings, unfinished pages, vague trust signals, unclear navigation, repeated guide text, and pages that only sell instead of helping. If the same issue appears in more than one area, it probably deserves a higher cleanup priority.
When a Site Clarity Audit is useful
Request an audit when you can see several public issues but need help deciding the order of operations. Eiway organizes visible cleanup signals into a report; implementation, private access review, and deeper fixes are separate decisions.