Indexloom Audit.
From a long issue list to a clear next step.
A personal SEO-audit project in progress, focused on prioritising sample findings, affected pages and proposed fixes in a planned audit workflow. No live crawler is connected.

- Project type
- Independent personal project
- Current work
- Interface & project planning
- Previews
- Two original interface screens
- Next milestone
- Functional build
A useful idea.
A considered direction.
The problem to solve
An audit is useful only if someone can decide what to do next. The planned experience prioritises explainable issues and affected URLs over a single unexplained score or a promise of search rankings.
Who it is for
Freelancers and small site teams reviewing a fictional example.com website. The dashboard is illustrative, not an audit of a real client.
Real development experience. Independent projects.
I have built client websites and web applications as part of an agency team. Those deliveries are separate from the independently branded projects shown here; client code, screenshots and private data are not reused.
A closer look at the project.
Explore the current interface direction and sample content. Open either preview for a closer look.
Audit overview
In progress · Illustrative content
Prioritised findings
In progress · Illustrative content
Where the project
is headed.
The intended user journeys that will guide the functional implementation.
Define the scope
A future scan flow would set an allowed domain, page limit and crawl rules before any network request is made.
Inspect a finding
The design groups a finding with its affected sample URL, severity and proposed next action. Demonstration counts are not measured results.
Track a fix
The planned workflow would recheck a finding and keep an audit history; neither re-crawling nor reporting runs on this portfolio page.
More than a
different colour palette.
An ink-dark sidebar and lime highlights frame a pale analytical workspace. Ordered findings, small trends and short explanations give the interface a tool-like feel without using third-party audit screenshots.
Explain the priority
The UI pairs each severity label with a reason, rather than presenting an opaque ranking guarantee.
Reserved example domains
Only example.com paths appear in the artwork. No client domains, accounts or private findings are reused.
Crawl safely
Robots handling, rate limits, URL validation and server-side request protections belong in the future backend requirements.
Progress so far.
The next milestones.
Original branding, two interface previews, a project brief and an implementation roadmap.
Implementation details will be added as the build progresses.
- 01NEXT MILESTONE
Will define a limited, explainable first set of audit rules.
- 02NEXT MILESTONE
Will build a scoped crawler with rate limits and request-safety checks.
- 03NEXT MILESTONE
Will store findings and implement per-project access control.
- 04NEXT MILESTONE
Will validate audit accuracy against test sites before displaying real results.
About this project.
Working brand names and sample content are created for these personal projects, not used as client testimonials or results.
What is the current project status?
This is a personal project in progress. The original branding, interface previews and project scope are in place. Functional implementation and integrations are the next milestones; the preview screens use illustrative data.
How does this relate to previous client work?
I have built client websites and web applications through an agency. That experience informs my work, but this is a separate personal project with its own brand and implementation plan. It is not a renamed client delivery or a completed copy of an employer project.
What do the previews demonstrate?
They show the current interface direction, content structure and planned user journeys. The backend, authentication and third-party integrations described in the roadmap remain planned, not completed engineering work.
How will progress be shown here?
As the personal build progresses, this page will be updated with verified features, implementation details and new screenshots. The project status will distinguish work in progress from a completed implementation.
Have a project in mind?
Let's discuss an original build around your requirements—not reuse an employer's work.
All previews stay inside this portfolio.

