Preparing for an SEO audit and interpreting limited results

• Prepare the public website address and a list of important pages. Private accounts and secret links are unnecessary for an initial review.
• Describe the main services, audience, language and market. Different pages may serve different search intentions.
• Record when you first noticed the issue and what changed on the website around that time.
• List known changes to the domain, page addresses, CMS or content in a short timeline.
• If you use Search Console, prepare an appropriate report export with its dates and filters. Do not send your account password.

Siteman's express check processes the submitted public address and up to two internal pages: no more than three in total. Check which addresses were processed and which steps remain incomplete.

Observations are based on the server response. This check does not calculate PageSpeed or real-user performance metrics. Heading hierarchy, image alt text and security headers require separate assessment. Do not turn this sample into an overall SEO score or a statement about rankings.

• Title and H1: was a heading found, and does it explain the page's purpose? A match in the sample does not automatically require rewriting every page.
• Description: review a missing description. Google may also build a search snippet from the page's own content.
• Canonical: a different target is not necessarily an error. Check that it represents the intended main version of the material.
• robots.txt and Sitemap: one sets crawling rules; the other helps URL discovery. A sitemap does not guarantee indexing.
• JSON-LD: the number of blocks and valid JSON syntax are separate observations. Correct syntax does not replace content checks or rich-result requirements.

HTTP 403, 429, 503, a CAPTCHA or a timeout can leave the check incomplete. Establish whether the tool received the same response as an ordinary visitor. An unavailable measurement should not be interpreted as a measured zero.

Respect any waiting time stated by the source. Use an authorised manual review instead of bypassing a CAPTCHA or sending frequent repeat requests. Failure to retrieve a page or file does not prove that it is absent from every possible location.

The Search Console search performance report includes clicks, impressions and other search metrics. When comparing periods, keep the search type, country, device and page filters consistent. Record the question that the selected view is intended to answer.

URL Inspection distinguishes information held in the index from a live test. A positive live test does not guarantee indexing. Before treating two screenshots as conflicting evidence, check their dates and which type of inspection each shows.

• Identify the page and the observation time.
• Describe the possible effect on the business task, such as inaccessible material, an incorrect destination or an unclear offer.
• Separate confirmed facts from hypotheses and identify a further check for missing information.
• After a change, repeat the same scenario on the same page rather than combining measurements that answer different questions.

Use Siteman's separate contact form to provide the public website address, important pages and the observation that concerns you. Access credentials, secret links and users' personal information are unnecessary for the initial request.