A free digital asset audit across five axes, not one
A free digital asset audit measures your live site on five separate axes — AEO answerability, AI crawler access, lab-measured Core Web Vitals, structured data validity and an automated accessibility scan against WCAG 2.2 A/AA criteria — and gathers the findings into one prioritised list. The report is delivered within five working days, costs nothing and creates no obligation to work with us.
Which five axes does the free digital asset audit cover?
The audit covers five axes together: AEO answerability, AI crawler access and llms.txt status, lab-measured Core Web Vitals, structured data validity, and an automated accessibility scan against WCAG 2.2 A/AA criteria. For every axis this page states what is checked, how it is measured and how it appears in the report.
The five axes are measured in the same run, so every finding rests on one date and one set of measurements. Up to 25 pages in the site's primary language are archived; heading and structured data checks run on those pages, while speed and accessibility measurements run on up to six sample pages, including the home page, selected from them by URL structure. Alongside these five axes, the report's summary check table also includes basic search engine checks, corporate trust checks and contact checks.
-
AEO answerability
AEO is the work of making a page directly quotable inside search answer boxes and AI assistants. On this axis we look at the measurable prerequisites of answerability: a single main heading that states the page's subject, headings written as questions, and text that can be read without JavaScript running.
-
AI crawler access and llms.txt
Generative search engines and AI assistants reach content with their own crawlers. On this axis we measure which crawler is allowed, which is blocked, and whether the rule applied is specific to that crawler or is the general rule. Blocking search or AI search crawlers for the whole site is marked as a gap in the report; for training crawlers the decision is yours, and their status is reported without a score.
-
Core Web Vitals — lab measurement
Core Web Vitals is the shared name for the loading, interaction and visual stability metrics of a page. On this axis loading (LCP) and visual stability (CLS) are assessed through repeated lab measurement on a mobile profile. INP, the interaction metric, cannot be calculated in a lab measurement that involves no user interaction, so TBT is reported in its place. Lab measurement does not represent real user experience; the report states this limit.
-
Structured data validity and coverage
Structured data is code that marks up information about the organisation, its services and its pages in a form machines can read unambiguously. On this axis we look at which schema types are used, whether required and recommended properties are filled in, and whether there are syntax errors.
-
Accessibility — automated WCAG 2.2 A/AA scan
WCAG is the set of Web Content Accessibility Guidelines published by the W3C. On this axis the sample pages are scanned with automated rules associated with the WCAG 2.2 level A and AA success criteria. Automated tools catch only some accessibility problems; the scan result is not a statement of conformance.
The upper threshold for a "good" Largest Contentful Paint. The threshold is defined for field data; the audit compares the lab median against this published threshold.
Source: Google web.dev — Largest Contentful Paint (LCP) · Accessed: 2026-09-15 Open the source (opens in a new tab)
Most thresholds are published criteria from sources such as Google, the W3C and Lighthouse. For checks with no published numerical threshold (for example, the share of pages with a single h1), we use our own threshold. The source of the checks behind each finding is given next to that finding in the report; the measurement log in the appendices records each check's criterion, its source and whether the threshold is published or our own.
Which kinds of findings can the report contain?
The table below shows examples of the finding types the audit can produce and how their business impact might be written; in the report, each finding's business impact is written separately to match the measured state. Which findings come out depends on your site; the order in the table is not a frequency ranking.
| Axis | Finding type | Example business impact sentence |
|---|---|---|
| AEO | Inner pages have no h1, or carry more than one | Because the page's subject is not stated in a single main heading, search engines and AI systems may find it harder to work out what the page is about. |
| AEO | A significant part of the home page text is only generated when JavaScript runs | Crawlers that do not run JavaScript may not see the main text; the content may not be usable as a source in those systems. |
| Crawler access | A search or AI search crawler is blocked for the whole site in robots.txt | The blocked crawler cannot crawl the page for its own search index; use of the content as a source in that service's answers may be limited. |
| Core Web Vitals | LCP above 2.5 seconds in the mobile lab measurement | On mobile, visitors may have to wait longer when the page first opens before they can see its main content. |
| Core Web Vitals | CLS above 0.1 in the lab measurement | Content that shifts while the page loads may cause a tap on the wrong link or make visitors lose their place in a form. |
| Core Web Vitals | TBT above 200 ms in the lab measurement | Because the browser stays busy running the page's scripts for long stretches, menus and forms may respond late to taps. |
| Structured data | The home page has no organisation markup, or its recommended properties are empty | Because company details are not defined in a form machines can read unambiguously, search systems may have to infer them from the page text. |
| Structured data | Pages contain a JSON-LD block with syntax errors | Because the faulty block cannot be read, all of the markup inside it may be ignored by search systems. |
| Accessibility | Form fields have no accessible label | A visitor using a screen reader may not be told what the field asks for; the enquiry form may be abandoned. |
| Accessibility | Text contrast is below the 4.5:1 threshold | Low-contrast text may remain illegible for visitors with low vision. |
The minimum contrast ratio for normal-size text (WCAG 2.2, Success Criterion 1.4.3, level AA). For elements with a contrast violation in the scan, the measured ratio is compared against this threshold.
Source: W3C — WCAG 2.2, Success Criterion 1.4.3 Contrast (Minimum) · Accessed: 2026-09-15 Open the source (opens in a new tab)
The rows above are example finding types; they do not belong to any specific company. We publish no example, screenshot or name from any company's report — your report is protected by exactly the same rule.
What does the report contain and how long does it take?
The audit delivers three things: a prioritised findings list, the measurement appendices and a 30-minute walkthrough call. The report is delivered no later than five working days from the day the scope is confirmed in writing; the walkthrough call is held after delivery. The written report is produced in Turkish; the walkthrough call can be held in English. There are three prerequisites: a live, publicly reachable site address, a corporate email address we can use to verify the request, and someone who will read the report.
What is delivered?
- Prioritised findings list Every finding carries at least the following: the check area the finding belongs to, the evidence (the measurement record, plus the affected pages for page-level checks), a one-sentence business impact, the proposed fix, an impact and effort estimate, and the source it rests on. The order follows business impact and estimated implementation effort — not the order of the technical headings. Impact and effort values are team estimates, not measurements.
- Measurement appendices The results file for all checks, the raw Lighthouse output closest to the median for each sample page and a summary of all measurements, the structured data audit output, the robots.txt downloaded on the day of measurement and the crawler rule mapping, the accessibility scan logs for each page, and mobile and desktop screenshots of the home page. The files are delivered as a single compressed file (zip), which also contains a readme explaining the tools, versions and measurement settings used.
- 30-minute walkthrough call One online session to read the report, answer questions and explain why a given item comes before another. No proposal is presented. If you want to discuss an engagement, just ask and we will arrange a separate meeting.
What are the prerequisites?
- A live, publicly reachable site Password-protected staging environments and unreleased designs cannot be measured. If a bot check in front of the site (for example a CAPTCHA or a queue page) blocks the measurement requests, the site cannot be measured reliably with this audit.
- A verifiable corporate email address We need it to connect the request to the company that owns the site. We do not audit a company's site on behalf of a third party without the company's knowledge.
- Someone who will read the report Marketing, IT or a decision maker — it makes no difference. One named person who will evaluate the findings is enough, and the walkthrough call is held with that person.
How do the five working days run?
-
Request and scope sign-off
The site address and the request's connection to the company are verified; the scope (one site address, five axes) is confirmed in writing in a single email. The audit begins only after that confirmation; your position in the queue is communicated the same day.
-
Crawl and measurement
Up to 25 pages in the site's primary language are archived; from these, up to six sample pages, including the home page, are selected by URL structure. Repeated lab measurements and an automated accessibility scan with axe-core are run on the sample pages; robots.txt and llms.txt are downloaded, and the structured data on the archived pages is checked against the rules for required and recommended properties. The measurement date and the Lighthouse, Chrome and axe-core versions are recorded.
-
Writing the findings
The measurement results are turned into findings. Every finding is linked to at least one measurement record and written with its evidence, a one-sentence business impact, a proposed fix and estimated impact and effort values. Impact and effort values are labelled in the report as team estimates.
-
Verification and prioritisation
The draft findings pass through a separate verification step that compares each sentence with the measurement files, and through a rule check. Sentences that are not supported by the measurements, that contradict them, or that contain a promise of results or a statement of conformance are corrected or removed from the report. The final order is calculated from the verified impact and effort estimates.
-
Delivery and walkthrough
The report and its appendices are delivered to you, followed by a 30-minute online walkthrough. When that call ends the engagement is complete; whether anything continues afterwards is entirely your decision.
What is this audit not?
This audit is not a sales call: the report contains no proposal. Nor is it the raw output of a single tool: every finding is linked to a measurement record, passes through a separate verification step and is written with its business impact. It carries no search ranking, traffic or revenue promise — no claim that measurement does not support is written into the report, and values that could not be measured are marked "could not be measured".
- It is not a sales call The report contains no price, proposal or package recommendation. The walkthrough exists to explain the findings. If you want to discuss commercial terms, just ask and we will arrange a separate meeting.
- It is not the raw output of a single tool Lighthouse, axe-core, HTTP and HTML measurements are combined into a single measurement file; the tables in the report are generated directly from that file, and the findings are written in business language.
- It carries no search ranking, traffic or revenue promise The audit measures the current state. Search ranking and revenue depend on price, product, competition and demand — variables outside the audit's control. The report shows the measured values, the thresholds they are compared against and the findings based on them; it makes no forecast of search ranking, traffic or revenue.
- It does not include writing code or applying the fixes Findings are written clearly enough to be implemented, but implementation is outside the scope of the audit. The fixes can be applied by your own team, by your current agency, or by us under a separate contract.
Which items does every report contain?
- Heading structure and question-form headings The single-h1 check, the number of question-form headings and the raw HTML text ratio on the home page.
- Search and AI crawler rules, llms.txt status The robots.txt rule that applies to each crawler group and the llms.txt response code; the full mapping is in the appendices.
- LCP, CLS and TBT: repeated mobile lab measurement Five measurements on the home page and three on each other sample page; the median and the range from lowest to highest.
- Structured data coverage and property rules The share of pages with JSON-LD, the recommended properties of the organisation markup, missing required properties and syntax errors.
- Automated WCAG 2.2 A/AA scan axe-core rules; checks the tool cannot resolve automatically are counted separately as "needs manual review".
- Every finding linked to a measurement record A finding without evidence does not enter the report.
- Every finding written with its business impact A one-sentence business impact and a proposed fix for every finding.
Automated tools give the first signal because they are fast and free; they are used in this audit too.
Who is this audit for, and who is it not for?
The audit suits companies that have a live corporate site and someone able to evaluate the findings. We cannot make time for requests with no site yet, requests that only want a price list, or requests that plan to use the report as leverage against another supplier. Saying so upfront protects both sides.
This audit suits you
- You have a live, publicly reachable corporate site — not a staging environment or a password-protected preview.
- There is a named contact who will read and evaluate the findings: marketing, IT or a decision maker.
- You run a multi-location business, a dealer or branch network, or a multilingual site; on multilingual sites only the primary-language version is measured.
- You want to discuss the technical prerequisites of search and AI visibility through measurement rather than assumption.
- You intend to implement at least one item from the report, whoever ends up doing the work.
- You already work with an agency and want a second opinion based on measurement.
This audit does not suit you
- You have no live site yet; in that case the subject is not an audit but a build.
- You are only after a price list; the audit report contains no proposal and no pricing.
- The report is wanted as leverage in a negotiation with an existing supplier.
- A search ranking, traffic or revenue guarantee is expected; we give no such undertaking.
- The site is a personal blog, a one-page brochure or a short-lived campaign page.
- The full report is expected to be published openly; the report is written for you alone.
The audit is free and carries no budget condition. If an engagement follows, we work at corporate scale on a project basis; we do not take one-off small jobs and point those requests politely towards smaller studios instead. The full distinction is set out on why we publish measurements, not claims.
What information does the audit request ask for?
Ten things: the site address, company name, industry, number of employees, your existing digital assets, your main concern, your name, your role, a corporate email address and a telephone number. The asset and concern selections are optional; the details are used to assess your request and reply to you with the report. The form calls no third-party verification service; a hidden field and a timestamp handle unwanted submissions.
What should you know about the audit before you apply?
Seven questions are answered below: whether the audit is really free, how long the report takes, whether you are obliged to work with us afterwards, whether WordPress sites are audited, how your data is handled, how it differs from automated tools, and whether sites outside Turkey are covered. Each answer can be understood when read on its own.
Is the audit really free?
Yes. No fee is charged, no invoice is raised and no line item is added later. The only thing we ask in return is that a 30-minute walkthrough can be held with someone able to evaluate the findings, and that call is a reading of the report rather than a sales presentation. We cap how many audits we take per week: measurements are run for only one site at a time, in sequence, and the walkthrough call for every report is held one to one.
How long does the report take?
At most five working days from the day the scope is confirmed in writing. Day one is scope sign-off, day two the measurements, day three writing the findings, day four verifying and prioritising the findings, day five delivery. The walkthrough call is scheduled after delivery. If anything is going to run late, we tell you in writing before the deadline passes, not after.
Am I obliged to work with you afterwards?
No. The engagement ends once the walkthrough call is complete: there is no contract, no deposit and no option right. You are free to implement the findings with your own team or with your current agency. The report is written clearly enough to make that possible: every finding states the measurement it rests on and its source; for page-level checks the affected pages are given, and for automated accessibility scan results and LCP and CLS issues the element concerned is also given.
My site runs on WordPress — is it still audited?
Yes. The audit is platform-independent: WordPress, WooCommerce, a custom application or a static site make no difference, because measurement is made on the output of the live page that reaches the browser. The same checklist is applied to WordPress sites: for example, script weight that makes a page slow to respond to taps is reported through the TBT value in the lab measurement.
What happens to my data during the audit?
The details you submit are processed only to run the audit and to reply to you; they are not passed to a third-party advertising, scoring or enrichment service. The report is yours: its contents are not published as an example and your company name is not used as a reference. Retention periods and your rights under Turkish data protection law (KVKK) are set out in our privacy and KVKK notice.
How does this differ from an automated audit tool?
The audit evaluates five axes together in the same measurement run; every finding is linked to a measurement record and written with its business impact. For example, a finding on pages that do not meet the single-h1 rule is given a one-sentence business impact such as "because the page's subject is not stated in a single main heading, search engines and AI systems may find it harder to work out what the page is about"; the sentence is written afresh in each report to match the measured state. The robots.txt rules for AI crawlers are also mapped per crawler.
Do you audit sites outside Turkey, and in which languages?
Yes. The site can be hosted anywhere, because measurement is remote. The written report is currently produced in Turkish; the 30-minute walkthrough call can be held online in English or Turkish. On multilingual sites only the primary language version is archived and measured; other language versions are not sampled.
If your question is not listed, send it through the contact page, or read every topic on the frequently asked questions page.
See the measured state of your website within five working days.
The audit is free and creates no obligation to work with us. The report itemises findings on AEO answerability, AI crawler access, lab-measured Core Web Vitals, structured data validity and accessibility (automated scan); every finding sets out its evidence, its business impact and a proposed fix.
We work with corporate-scale, multi-location or multilingual organisations. One-off small jobs fall outside our scope; in that case we point you to smaller studios. Baki Bilisim · İzmit / Kocaeli, Turkey · +90 507 817 27 17 · bilgi@bakibilisim.com