FAQ
Frequently asked questions
Clear answers about wallet credit, usage, subscriptions, and how Tycoon charges for work.
We use Next.js — doesn't framework-level optimization handle most of this?
Framework defaults get you 60-70% of the way: next/image, App Router with SSR, automatic sitemap. The other 30% is what breaks in practice: your new /pricing page uses a <img> tag instead of next/image and tanks LCP. Your blog writer added a /use/[model] page without a canonical tag. A content migration created 800 duplicate pages. Tycoon catches these framework-level escapes — the stuff that bypassed your best practices and is silently hurting rankings.
What's the difference between this and just running Ahrefs Site Audit monthly?
Ahrefs is a data source, not an action system. It tells you there are 247 issues; it doesn't fix them, prioritize them by traffic impact, open PRs, or track fixes to completion. Tycoon uses Ahrefs (and Screaming Frog, and GSC, and PageSpeed) as inputs, then adds the layer that turns 'audit finding' into 'merged PR'. Think of it as: Ahrefs = diagnosis; Tycoon = treatment + follow-up.
Our site has 80,000 URLs from programmatic SEO. Can auditing scale to that?
Yes, with sampling. AI Head of Content stratifies: top 500 pages by traffic get daily monitoring, next 5000 get weekly, long-tail gets monthly spot checks. Issues at scale (e.g., 2,000 pages missing schema) get batch-fixed via template update, not page-by-page. Programmatic SEO specifically needs this — manual audits don't work at that scale, and skipping audits is how Google penalizes you for thin content.
What about JavaScript rendering issues — my SPA doesn't render in Googlebot?
AI CTO runs a 'rendered vs source' diff on critical pages: compares raw HTML source to what Googlebot sees post-JS (via Rendertron or Google's Mobile-Friendly Test API). Mismatches flagged as rendering issues. Usual suspects: client-side routing without SSR fallback, content behind a data fetch, React hydration errors. Fix recommendations are framework-specific (add generateStaticParams in Next.js, use SSR in Remix, etc.).
Does it handle international SEO — multiple countries, multiple languages, with different domain structures?
Yes. Handles all three structures: subdirectories (/en, /es, /de), subdomains (en.site.com), and ccTLDs (site.fr, site.de). Checks: correct hreflang on every page, reciprocal declarations, x-default for language picker, locale-specific schema (currencies, addresses), localized sitemaps, country-specific GSC properties. The most common failure mode is hreflang asymmetry (en page declares es version, but es page doesn't declare en) — Tycoon catches these and auto-fixes.