emerchantpay
An initial deterministic pass across emerchantpay.com — AI-crawler access, crawlability, schema, rendering, and semantic structure. Each item is a pass/fail call, not an opinion. A full audit follows once we engage.
Escalated — critical findings could block visibility
Takeaways — what could block visibility
3 criticalHomepage is a JS-only shell — 0 anchor tags in raw HTML
High effortBing, most AI crawlers, and any crawler that does not execute JavaScript see an empty page with no links, meaning emerchantpay.com's homepage delivers zero navigable signals and zero topical content to a significant slice of the discovery ecosystem.
No H1 heading rendered in server-side HTML
Medium effortWithout a server-rendered H1, search engines and AI models cannot confirm the page's primary topic from raw markup alone, weakening topical authority signals for every crawler that relies on static HTML.
ChatGPT cannot retrieve the homepage
Medium effortWhen users or researchers ask ChatGPT to summarise or cite emerchantpay.com, the model returns no content from the site, removing the brand from AI-generated shortlists in a channel that is increasingly influential in B2B fintech vendor selection.
Technical scorecard
7 pass · 6 flagged across 13 deterministic checks. Site clears the basic crawl-accessibility bar with a few hygiene issues. Good candidate for an SEO engagement focused on growth, not rescue.
Claude
PassCan fetch and read the homepage
Claude's fetch tool (claude-sonnet-4-6) returned a successful retrieval status for https://www.emerchantpay.com/. When a user pastes this URL into Claude, the assistant accesses the page.
ChatGPT
CriticalCannot read the homepage
ChatGPT's fetch/search tool did not return content from this URL (no_citation_for_target_host). Could be a site-side block, missing index entry, or the model skipped the tool — we can't distinguish from this probe alone.
Gemini
PassCan fetch and read the homepage
Gemini's fetch tool (gemini-2.5-flash) returned a successful retrieval status for https://www.emerchantpay.com/. When a user pastes this URL into Gemini, the assistant accesses the page.
Crawler access policy published
Passrobots.txt found and reachable (223 bytes).
Sitemap location is referenced in robots.txt
Passrobots.txt points to 1 sitemap location(s): https://www.emerchantpay.com/sitemap_index.xml
Robots.txt restricts crawlers on specific URL patterns
Lowrobots.txt has Disallow rules for 12 tracked bots (Googlebot (partial), Bingbot (partial), Bytespider (partial), GPTBot (partial), ClaudeBot (partial), ImagesiftBot (partial) + 6 more), but only on specific URL patterns (e.g. `/wp-content/plugins/`). The site itself remains indexable; these patterns are typically utility URLs (admin paths, query strings, internal endpoints) and not a pre-qualification blocker.
Preferred URL is declared (canonical tag present)
PassCanonical URL declared: https://www.emerchantpay.com/
No bot-protection layer detected
PassNo Cloudflare, Akamai, DataDome, Imperva, or PerimeterX bot-protection signatures in the response headers.
Homepage requires JavaScript to display its content
CriticalOnly 54 characters of readable content in the raw HTML (19,814 bytes total). The page relies on JavaScript to render — Google handles this, but Bing and most AI crawlers do not.
Homepage has thin server-rendered content
CriticalOnly 54 characters of readable content render directly in the HTML. This is below the typical threshold for a homepage and may signal weak topical signals to search engines.
No <a> tags found on homepage
High0 `<a>` tags — page may rely on button/onclick navigation or be a JS shell.
Homepage has no main heading
MediumThere is no main heading (H1) on the homepage. This is the strongest signal search engines and AI crawlers use to understand what the page is primarily about — without it, the page's topical authority is weaker.
Structured data present (2 block, 5 schema type(s))
Pass2 valid structured-data block(s) on the homepage. Schema types declared: BreadcrumbList, FAQPage, Organization, WebPage, WebSite.
Want to walk through the fixes together?
A 30-minute call to triage the failures, agree what blocks publishing, and slot the remediation into the content engine setup.
