byteflowtech.in
AI engines can read, parse and attribute this brand.
Answer engines can reach your site, read it, and resolve your brand as a specific entity. The technical prerequisites are in place.
Read this before you act on anything below
A measurement of whether AI answer engines can reach your website, read it, and resolve your brand as a specific entity. Every line of it was tested against your live site during the run — nothing is looked up from a database or inferred from a third-party crawl.
It is not a measure of whether ChatGPT, Gemini or Perplexity currently recommend you. That is a different question with a different answer, and it needs a set of buyer questions run repeatedly across those engines — because answer engines are not deterministic, and a single run cannot support a claim about movement. We keep the two numbers apart deliberately. A vendor who merges them into one number is quoting you noise.
Five bands, weighted by consequence
Open any band to see what it measures and why it is worth what it is worth. Points lost are shown against the band's own weight, so you can tell where your score actually went.
AI Crawler AccessCan an AI engine physically reach your pages?
100%
−0.0 of 30 pts
This is the gate. Everything else is downstream of it.
What we measure
Two separate things, because they disagree more often than people expect. First, what your robots.txt gives each AI crawler permission to do. Second, what your server actually does when 24 real AI crawler user-agents knock on the door — which is a different question, and the one that decides the outcome.
Why an answer engine cares
A crawler that cannot fetch your page cannot cite you, no matter how good the page is. Blocking OAI-SearchBot removes you from ChatGPT's answers. Blocking PerplexityBot removes you from Perplexity's. There is no partial credit and no workaround: this is binary.
What good looks like
robots.txt names every AI crawler you want and allows it explicitly, private paths stay disallowed, and the live probe returns HTTP 200 for every crawler that matters.
Machine ReadabilityOnce fetched, can a model extract an answer from the page?
77%
−5.8 of 25 pts
A page that needs JavaScript to show its content is an empty page to an AI crawler.
What we measure
Whether your content exists in the HTML that is actually served — before any JavaScript runs — and whether it is shaped so an answer can be lifted out of it: real headings, a direct answer near the top, a title and description that say something, and enough words on the page to constitute a source.
Why an answer engine cares
AI crawlers do not run your JavaScript. Almost none of them do, and the ones that sometimes do will not wait. A React or Vue site that renders client-side serves an empty shell to every crawler, which is why a beautiful site can score badly here and a plain HTML page can score perfectly.
What good looks like
Server-rendered or statically generated HTML, one clear H1, a 40–60 word direct answer near the top of every important page, descriptive headings, and a title and meta description written for a human.
At 77%, this is what it costs you
You get fetched and then skipped. The crawler came, found nothing quotable, and moved to whoever answered the question in the first paragraph.
Structured DataIs your brand a machine-resolvable thing, or just words on a page?
100%
−0.0 of 20 pts
Structured data is how a model knows the name on your page refers to a real, specific company.
What we measure
Your JSON-LD: whether an Organization or LocalBusiness block exists and is valid, whether FAQ, Service, Product, Article and Breadcrumb types are used where they apply, and whether the entity carries the identifiers that let a model tell you apart from a similarly-named company.
Why an answer engine cares
Models resolve entities, not strings. Without structured data your brand name is text that has to be guessed at from context — and when another company shares your name or category, the guess frequently goes the other way. We found exactly that on our own domain: a near-identical brand name in the same country and category, and the model was quoting their facts about us.
What good looks like
Valid Organization or LocalBusiness JSON-LD on every page, sameAs links to your real profiles, a consistent legal name, FAQPage markup on pages that answer questions, and Breadcrumb markup for structure.
Discoverability & IndexAre you in the indexes AI answers are drawn from?
71%
−4.3 of 15 pts
ChatGPT Search and Copilot read Bing. If you are not in Bing, you are not in either.
What we measure
Sitemap presence and health, whether the sitemap is declared in robots.txt, canonical consistency, whether www and non-www agree, whether your 404 handling is honest, whether feeds exist, and whether IndexNow is set up so new pages get picked up in hours rather than weeks.
Why an answer engine cares
Answer engines do not crawl the open web from scratch on every question. They read indexes. Bing's index feeds ChatGPT Search and Microsoft Copilot; Google's feeds AI Overviews and Gemini grounding. Absence from an index is absence from everything built on top of it.
What good looks like
A clean sitemap declared in robots.txt, consistent canonicals, one host that redirects to the other, Bing Webmaster Tools verified, and IndexNow keys live.
At 71%, this is what it costs you
Slow discovery at best, permanent invisibility at worst. Most Indian sites we audit have never been submitted to Bing at all — six of our own properties had Bing Webmaster Tools accounts with zero sitemaps in them.
Trust & Entity SignalsDoes a model have any reason to name you specifically?
73%
−2.7 of 10 pts
Being readable makes you quotable. Trust signals make you worth quoting.
What we measure
Whether a real organisation is visible behind the site: a named entity, a physical address, contact routes, an about page with substance, authorship, and dates that show the content is maintained.
Why an answer engine cares
When an engine picks three sources out of a hundred candidates, it favours the ones that look accountable. An anonymous page with no address, no author and no dates loses to a page that has all three, even when the content is comparable.
What good looks like
A real about page, a postal address, a named team, working contact routes, visible publication and update dates, and consistent identity across your own profiles.
At 73%, this is what it costs you
You stay a source of last resort. You will be read, occasionally quoted, and rarely recommended by name.
Full plain-English guide to every band: what your score means →
87 → about 93 out of 100
Those three checks are currently withholding 5.6 points between them. This is arithmetic on the scoring, not a forecast.
Ordered by points recoverable
Not by how alarming the label sounds. A partly-credited heavy check outranks a fully-failed light one, because fixing it returns more of your score for the same afternoon.
Sub-headings phrased as real questions
Question headings match the shape of a user prompt, which is how retrieval picks the passage it will quote.
www / non-www resolve to one canonical host
Two live hostnames split every citation and backlink signal in half.
Title and meta description are specific and sized right
These two strings are frequently the entire snippet a model sees before deciding whether the page is relevant.
IndexNow key file in place
IndexNow pushes new and changed URLs into Bing within minutes instead of weeks — and Bing's index is what ChatGPT Search reads.
Answer-first block near the top of the page
Models quote extractable spans. A page that opens with a hero slogan and no declarative answer gives the model nothing to lift.
Content carries a named author
Anonymous content is systematically discounted against attributed content.
Outbound citations to authoritative sources
Citing primary sources is a documented quality signal and raises the odds of being cited back.
RSS/Atom feed available
Feeds are a cheap, machine-readable freshness signal for aggregators and crawlers.
Healthy text-to-markup ratio
A page that is 97% markup and script costs the crawler budget and yields little usable content.
Name, address and phone stated in plain text
Models cross-check NAP against directories and GMB; missing details weaken the entity match for local prompts.
Every check, with the evidence and the fix
All 46 findings, the complete crawler matrix, the method section and the request-budget record. A copy is on its way to [email protected].
Get a call about byteflowtech.in
Fifteen minutes, with your report open in front of both of us. We go through what is actually costing you points, what order to fix it in, and what you can safely ignore. No deck, and nothing is sold on the call.
Request a callback Or see the plans
We already have your number from the verification step — the form just asks when suits you.
Is AI already sending you visitors?
The audit answers whether engines can read you. This answers whether people are actually arriving from them — a fact that only exists in your own logs, which is why nobody can measure it for you from outside.
Paste one line before </body>
It records the referring host when a visit arrives from an AI assistant, and nothing else. No cookies, no IP address, no fingerprint, no third-party request. Read it first — it is about fifteen lines.
<script async src="https://namedrank.com/px.js?k=b2160719ede0430d874c"></script>
Your dashboard is already live
It will start filling the moment the first assistant referral lands. Bookmark it — the link is the only credential, so keep it to yourself.
Or use your own analytics instead
Would rather not add a line of anything? The GA4 recipe pulls the same number in about two minutes, and we get no data from it at all. See the recipe →
How this was measured
Measured live, just now
Every line was tested against https://byteflowtech.in during this run. Nothing is looked up from a database or inherited from a third-party crawl, and you can reproduce any finding with curl.
Your server was not hammered
Requests were spaced deliberately, with a hard per-host budget and a circuit breaker that stops the run if your server pushes back. Anything skipped is marked "not tested" and excluded from scoring.
Rate limits are not blocks
A 429 or a burst-triggered 403 is treated as inconclusive and left out of the score. Reporting our own impatience as your firewall's policy would be the easiest lie in this category to tell.
JavaScript is not executed
Deliberately, because AI crawlers do not execute it either. If a page renders client-side and scores badly here, that is the correct result rather than a limitation of the test.
Want this fixed rather than documented?
The Sprint takes your report as its scope of work — so there is nothing to discover, nothing to scope, and nothing to argue about.