Sample method photograph6documented observations
- 01SurfacePublic page and response
- 02ContextInterest leaks before the call
- 03DecisionEvidence-backed next step
← All industriesLaunch vertical
Common public-path risk · Interest leaks before the call
Independent Professionals
The public presence is scattered across a profile, a portfolio link, and a booking tool that do not agree on what you offer or how to start. A visitor who is ready to reach out cannot find a single obvious next step, so they default to 'I'll think about it' and never come back.
Public pages only. The $97 report comes after the result.
Public pages onlyInspect the method →
Sample method photographObservation register · source-bound
What Revvye can inspect on this public path.
These are sector-specific observation prompts from the industry registry. Your result only includes signals the scan actually detects.
- 01
Whether your website, your primary directory profile, and your social bios agree on what you actually do and who you do it for.
- 02
Whether there is one obvious next step for an interested visitor, not three competing links to a contact page, a calendar, and a DM.
- 03
Whether your portfolio or work samples are reachable from the page a prospect actually lands on, not buried behind a separate site.
- 04
Whether testimonials or reviews name the specific work you want to be hired for, not generic praise.
- 05
Whether your rates, packages, or engagement shape are signaled anywhere public, so unqualified inquiries self-select out.
- 06
Whether AI crawlers can read your bio and services page, or only see a thin link-in-bio landing screen.
Public failure patterns
Described. Not claimed.
These are documented sector patterns, not customer findings. A scan must observe the signal on your URL before it becomes part of your result.
- 01
A link-in-bio page that sends every visitor to five destinations with no indication which one is the actual next step.
- 02
A portfolio hosted on a separate platform that is never linked from the page a prospect actually searches for and finds.
- 03
A booking calendar embedded with no context, so a stranger is asked to pick a 30-minute slot before they know what the call is for.
- 04
Testimonials copied verbatim from a group chat screenshot with no name, date, or specific project attached.
- 05
A bio that reads identically across three platforms except for the platform-specific hashtags, so no single page earns the click.
Fix posture · after observation
A sequence for deciding what to change first.
This is a sector playbook, not a promised outcome. The detected evidence still determines whether any step belongs in the actual work order.
- 01
Pick one destination as the real front door and point every other profile at it.
- 02
Name the specific outcome you help people reach, not a role title alone.
- 03
Put one small next step in front of the booking link for visitors who are not ready to commit thirty minutes yet.
- 04
Attribute every piece of proof with a name, context, and date so it reads as real.
Published rule boundary
Sector context cannot invent a rule match.
The scan engine exposes 43 named public checks. Relevant rule definitions appear here only when the sector registry cites their real ids.
CRAWLER_BLOCKED_BY_ROBOTS_TXTAI crawler disallowed by robots.txt
Observes
robots.txt fetched from the domain root · per-bot Allow/Disallow evaluation via robots-parser · the matched robots.txt line number for the blocking rule
Does not measure
Detects only what robots.txt declares for the named bots Revvye tracks; it does not verify whether the engine actually honored the rule, nor whether the bot was blocked by a firewall/WAF the scanner cannot see.
markup.viewport-missingMissing viewport meta tag
Observes
<meta name="viewport"> presence
Does not measure
Checks the tag exists; the actual mobile rendering (overflow, CTA position) is graded by the mobile-experience worker checks.
homepage_missing_schemaHomepage has no detected schema markup
Observes
the schema_summary derived from the homepage during the scan
Does not measure
A presence signal at the homepage level; rich-result eligibility detail is graded by the Structured Data rules above.
Sector boundary questions
What the public scan can—and cannot—answer.
01I don't have a traditional website. Can Revvye still scan me?+
Yes. Revvye evaluates whatever public surface a prospect would actually land on, including a link-in-bio page, a portfolio platform profile, or a directory listing. The scan follows the same path a real visitor would.
02Will Revvye tell me to raise my rates?+
No. Revvye does not make pricing recommendations. It flags when the public surface gives a prospect zero signal about scope or rate, which tends to produce more unqualified inquiries than an operator wants to field.
03What if most of my work comes from referrals, not my website?+
The scan still applies. A referred prospect almost always checks the public profile before reaching out. Revvye checks whether that profile confirms what the referrer already told them.
04If I only have a link-in-bio page, can AI assistants still describe my work?+
They can only describe what they can fetch. A link-in-bio wall of five destinations with no offer statement is hard for a person and a crawler. Revvye follows the same public path a prospect would, including whether the destination page states the work, the next step, and whether robots.txt blocks it.
Observe the path before prescribing the fix.
The sector pattern is context. Your URL supplies the evidence.Return to the scanner →
Run this sector against your URL.
Public pages only. The $97 report comes after the result.