Crawl paths
Evidence-backed issue register grouped by affected template and commercial importance
Technical SEO SPECIALIST
Technical SEO your development team can act on.
A long crawl report is not a delivery plan. I investigate the issues that affect important pages, distinguish genuine constraints from low-value warnings, and turn the findings into prioritised fixes with clear acceptance criteria.
- A clear commercial objective
- Hands-on work, directly with me
- Priorities you can act on
7+Years of experience
50+Projects completed
1:1Direct collaboration
A clearer plan, page by page
● ● ●YOUR BUSINESS / YOUR NEXT CHAPTER
Technical SEO
Remove friction beneath the surface.
CLARITY RELEVANCE ACTION
THE WORK IN FOCUS
✓Crawl paths reviewed
✓Canonical signals checked
✓Rendering investigated
✓Fixes prioritised
An illustration of the approach, not a live audit.
BUILT AROUND YOUR BUSINESS
Remove friction beneath the surface.
For teams managing migrations, complex templates, JavaScript sites, large catalogues, or unexplained visibility losses. The work is most valuable when development resources are limited and you need to know what deserves a release slot.
Indexation
Prioritised implementation backlog with dependencies, effort assumptions, and ownership
Rendering
Reproducible developer briefs and acceptance criteria for agreed fixes
Release checks
Release validation record with resolved issues, remaining risks, and monitoring priorities
EXPLORE THE WORK
See what I
actually work on.
Choose an area to explore the work and what you receive.
ILLUSTRATIVE WORKING EXAMPLE / 01
A clearer route to your important pages
Resolve conflicting signals and give developers a prioritised, testable implementation brief.
Concept illustration · no client performance dataWHAT I REVIEW
Crawl paths
Combine crawl findings, Search Console evidence, template sampling, and server logs where available to identify which commercially important URLs are affected. Distinguish symptoms from the underlying cause.
YOUR DELIVERABLEEvidence-backed issue register grouped by affected template and commercial importance
ILLUSTRATIVE WORKING EXAMPLE / 02
Indexation · Technical SEO
Review status codes, redirect chains, canonical signals, robots directives, sitemaps, and internal discovery paths. Define intended behaviour for duplicates, retired pages, and parameter-driven URLs.
Concept illustration · no client performance dataWHAT I REVIEW
Indexation
Review status codes, redirect chains, canonical signals, robots directives, sitemaps, and internal discovery paths. Define intended behaviour for duplicates, retired pages, and parameter-driven URLs.
YOUR DELIVERABLEPrioritised implementation backlog with dependencies, effort assumptions, and ownership
ILLUSTRATIVE WORKING EXAMPLE / 03
Rendering · Technical SEO
Inspect rendered content, link availability, mobile behaviour, and field performance data where sufficient data exists. Reproduce template-level issues and document the conditions under which they occur.
Concept illustration · no client performance dataWHAT I REVIEW
Rendering
Inspect rendered content, link availability, mobile behaviour, and field performance data where sufficient data exists. Reproduce template-level issues and document the conditions under which they occur.
YOUR DELIVERABLEReproducible developer briefs and acceptance criteria for agreed fixes
ILLUSTRATIVE WORKING EXAMPLE / 04
Release checks · Technical SEO
Turn findings into developer tickets with affected examples, business relevance, dependencies, and acceptance criteria. Validate the agreed releases and keep unresolved risks visible.
Concept illustration · no client performance dataWHAT I REVIEW
Release checks
Turn findings into developer tickets with affected examples, business relevance, dependencies, and acceptance criteria. Validate the agreed releases and keep unresolved risks visible.
YOUR DELIVERABLERelease validation record with resolved issues, remaining risks, and monitoring priorities
A FOCUSED PROCESS
Clear steps.
Shared expectations.
We agree the scope and responsibilities first, then move from investigation to implementation and review.
Discover
Understand your business, your audience, and the problem you want to solve.
Prioritise
Agree what matters most and the work that fits your resources.
Implement
Deliver the agreed recommendations and coordinate the necessary changes.
Review
Check the work, interpret the evidence, and decide the next useful action.
EXPERIENCE IN THE DECISION
What I look at
before recommending work.
Technical prioritisation starts with affected pages and business impact. A recurring error on a revenue-bearing template may deserve attention before thousands of cosmetic warnings. I explain what the evidence supports, what still needs investigation, and what the team can reasonably defer.
Review my professional experienceILLUSTRATIVE DECISION BRIEF
The situation
Filtered URLs multiply while important category pages have inconsistent canonical signals.
The decision
Define which filters have useful search demand, then agree crawl, indexation, canonical, and linking rules with developers.
The review
Validate representative templates and monitor the intended URL groups after release.
THE DIFFERENCE IN PRACTICE
From scattered activity
to purposeful work.
An illustrative comparison of the approach. These examples describe improvements to the work, not promised performance results.
A COMMON STARTING POINT
Activity without a clear connection.
- Conflicting canonical signals
- Important pages buried
- Fixes without validation
THE INTENDED DIRECTION
Relevant, structured, accountable.
- Consistent preferred URLs
- Clear discovery paths
- Documented release checks
BEFORE WE BEGIN
A clear scope.
No guesswork.
Define the domains, templates, environments, migration stage, and available access before the audit. Development, hosting changes, release management, and ongoing monitoring need named owners. A migration requires its own pre-launch and post-launch scope.
What I’ll need from you
- Search Console access where available
- Details of migrations or recent site changes
- A contact for your CMS or development team
How we review progress
Track the intended indexation and crawl behaviour of priority URL groups, implementation completion, and relevant organic landing-page performance. Use field performance data when available; a perfect third-party audit score is not the objective.
WORKING WITH BARSHAD
Senior input.
Clear accountability.
My 7+ years in SEO and digital marketing inform how I investigate, prioritise, and communicate the work. You work directly with the person responsible for the recommendations.
For owners & leadership
Start with the business objective and the economics behind it. The proposal sets out priority work, dependencies, fees, and how we will assess progress. Where evidence is incomplete, assumptions remain visible.
For marketing & delivery teams
Agree the backlog, implementation owner, review cadence, and approval process. Recommendations include the reasoning and practical handoffs your writers, developers, or account team need.
For hiring managers
Use my CV and experience summaries to assess role fit, responsibility, and how I approach the work. My SEO leadership background includes Kazix and Yoddha Lab; the portfolio distinguishes CV-based experience from verified client case studies.
View background & CVAgree the engagement before delivery.
A diagnostic project, implementation sprint, or ongoing partnership should each have a written scope, named owners, a review schedule, and a clear approach to additional work. Fees depend on complexity, delivery responsibility, and the agreed scope.
TOOLS THAT SUPPORT THE WORK
Good tools. Considered judgement.
The toolset depends on your site, access, and the agreed scope.
Google Search Console
Screaming Frog
Google Tag Manager
Microsoft ClarityYOUR QUESTIONS, ANSWERED
A little clarity
before we talk.
Can you work inside our development workflow?
Yes. We agree the ticket format, access, engineering contact, staging checks, and release responsibilities. Recommendations include enough evidence for the team to reproduce and validate the issue.
Does the audit include implementing every fix?
Implementation ownership is explicit in the proposal. I can investigate, specify, and validate the work; changes requiring your engineering or hosting team are identified before delivery.
Who will I work with?
You work directly with Barshad. We agree any developer, writer, or internal-team responsibilities as part of the scope.
How are timelines and fees agreed?
After reviewing your requirements, we agree the priority work, deliverables, dependencies, timeline, and fees before starting.
Do you guarantee specific results?
No. Rankings, demand, competition, platform changes, and implementation affect results. I commit to clear work, transparent priorities, and evidence-led review.
Can you work with my existing team?
Yes. Share your existing workflow and available resources so we can agree ownership, handoffs, and the support your team needs.
Crawling, rendering, indexing and architecture
01 / DELIVERWhat the work produces
An issue register with examples, severity, implementation owner and acceptance checks. Review canonicals, redirects, robots directives, sitemaps, pagination and template behaviour where relevant.
02 / EVALUATEHow we assess it
Validate released changes, inspect representative URLs and monitor the affected page groups. More indexed URLs alone is not the objective.
03 / ALIGNBefore work starts
Agree the business objective, baseline, access, implementation owner and review period. Prioritise by likely impact, effort, dependencies and business relevance.
YOUR WEBSITE. YOUR NEXT STEP.
Let’s make the work
worth doing.
Share your website and the challenge you want to solve. Let’s start with a useful conversation.