Crawling and indexing review
Status codes, robots, noindex, sitemaps and internal links; cross-check with Search Console when access is available.
What is keeping your pages out of Google?
Technical SEO with Nir Levi: crawling, indexing, rendering, canonical URLs, internal links and multilingual websites, with actionable developer recommendations.
Prepare your inquiryTechnical SEO
I want your team to get more than a list of errors from an audit. We’ll investigate which issues affect important pages, what needs fixing and how to verify the changes.
- Important pages are difficult to discover or are not being indexed.
- A platform, domain or website structure change is planned.
- Rendering, duplicate URLs or language versions need investigation.
What will you receive?
Page and template review
Initial HTML, rendering, canonical URLs, hreflang and structured data that matches visible content.
Developer-ready tasks
Affected URL examples, an explanation of each issue, priorities and acceptance criteria.
Verification after implementation
Recheck fixes within the agreed scope and document what is resolved and what remains open.
The audit passed. Did the task finish?
If visitors need to complete a form, find a document or download a file, the technical review can include one defined journey. Start with the outcome the user needs and agree on the test environment and permissions.
- Define the input, expected result and evidence of completion, such as a file that opens with the expected data.
- Record a valid attempt and an error case, including whether the agent can understand the message and recover.
- Separate tool scores from task outcomes and deliver findings with reproduction steps, an owner and acceptance criteria for retesting.
Findings apply to the journey, agent and version tested. This is not certification for every AI agent or a ranking promise. Submission, login and payment tests use only the agreed environment and permissions.
Documented example: the form defect Lighthouse missed ↗
Discuss the journey you need testedHOW WE CHECK PROGRESS
Track verified fixes, crawl access to important pages and indexing changes. Assess user experience separately, distinguishing lab tests from real-user measurements.
From the first question to the next move.
- 01
Understand
Define the challenge, objective and data needed.
- 02
Investigate
Gather evidence about the website, content and competition.
- 03
Prioritize & implement
Build a plan and work with your teams within the agreed scope.
- 04
Measure & refine
Review what changed and decide what comes next.
Good questions. Clear answers.
Does the audit include code changes?
The audit supplies findings and developer tasks. Implementation support and fix verification are agreed as part of the engagement scope.
Does every SEO tool warning need a fix?
No. Prioritize by likely impact on important pages, supporting evidence and effort, rather than the number of alerts.
Can you review a site before launch?
Yes. Define the test environment, expected URLs and migration plan, then verify the production website after launch.
