twitterapi.io
1 page · 0.1s · Scanned just now
Mostly human-written
62% confidence
The score is a fingerprint of automation, not a quality judgment. A high score means the page reads as machine-generated. It doesn't mean the page is bad.
- Page title
- Real-Time API for Public Social Data — Affordable, No Limits
- Meta description
- Build with an affordable real-time API for public social data. Read user feeds, search posts, and publish — predictable per-call pricing, no minimums, no rate-limit surprises.
- Final URL
- https://twitterapi.io/
- Language
- en
- Built with
- Next.js
This page blends marketing language with substantive product detail and genuine user testimonials. The structure avoids boilerplate templating; the content mixes cliché (world's fastest/most affordable) with specifics (sub-5min setup, $0.15/1K, 500ms latency, verified Trustpilot reviews with real user voices). The complete absence of imagery is unusual but not an AI signal. Testimonials show inconsistency in voice and stakes-driven feedback, authentic markers. Confidence is moderate due to thin imagery signal and some generic marketing phrasing, but structure and tone point away from full AI generation.
- Worth notingContent
Marketing clichés mixed with specific pricing and performance metrics create uneven register.
Evidence- “The world's fastest, most affordable, and most reliable API”body
- “$0.15 per 1K units”body
- “< 5 minutes”body
Try thisStrengthen the opening claim with one concrete differentiator (e.g., 'Real-time streams at 500ms latency for $0.15 per 1K units') instead of stacking superlatives.
- Worth notingStructure
Comparison table uses generic column labels ('Official API', 'Other Providers') that obscure competitor names.
Evidence- “Features”H3
- “Official API”body
- “Other Providers”body
Try thisReplace 'Official API' and 'Other Providers' with actual competitor names or product names to strengthen credibility and differentiation.
Signals of human authorship the page is doing well.
- Tone
Trustpilot testimonials carry distinct voices with specific use-cases (academic research, hobbyist developers, production use) and genuine criticism ('latency can spike up to 1m').
- Content
Page leads with measurable claims tied to actual metrics: sub-5 minute setup, $0.15/1K pricing, 500ms latency, 4.6 star rating with 28 verified reviews.
- Content35
Mix of genuine product details (sub-5min setup, $0.15 per 1K units) and mild marketing phrasing ("world's fastest, most affordable"); Trustpilot testimonials are verbatim user reviews with identifiable voices and specific praise.
- Structure25
Non-templated layout: comparison table, Trustpilot badge, testimonial carousel, FAQ section — custom structure, not standard hero→features→CTA template.
- Imagery18
Zero images on page; no stock photos, no AI-generated visuals, no imagery signal at all — unusual for a SaaS landing page but not an AI indicator.
- Tone38
Testimonials carry distinct voices ("HUMAN!!!", "nitpicking improvements", regional slang); marketing copy is functional but occasional clichés ("The world's fastest, most affordable, and most reliable API").
- Words913
- Images0
- Alt coverage100%
- Internal links8
- External links11
- Schema blocks2
- HTML size139 KB
Common AI writing tells we counted in the body text. A few hits is normal. A dense cluster is the signal.
Show counted phrases1 match across 1 phrase
- “comprehensive”×1
- Meta tagsMissing canonicalWhy this matters
Why it matters. Title and description are the two strings Google shows in search results. They decide whether anyone clicks. A canonical tag tells Google which URL is the source of truth when the same content lives at multiple paths.
Passing looks like. A non-empty title under 60 characters, a meta description under 160, and a self-referencing canonical link.
Fix. Add the missing tags inside the page head. Treat the title as a headline you'd want to read in a SERP, not a brand slogan.
- Heading structure1 H1, 4 H2Why this matters
Why it matters. Headings are how crawlers and assistive tech understand a page's outline. One H1 names the page. H2s break it into sections. Skipped levels and missing H1s confuse both.
Passing looks like. Exactly one H1, at least one H2, and no skipped levels (no H1 to H3 jumps).
Fix. Replace the missing or duplicate H1 with a single, descriptive heading. Promote section titles to H2. Demote sub-points to H3.
- Mobile readinessResponsiveWhy this matters
Why it matters. Google indexes mobile-first. A page without a responsive viewport renders zoomed-out on phones, fails Core Web Vitals on touch, and loses its mobile ranking.
Passing looks like. A meta viewport tag with width=device-width and a layout that reflows under 600px.
Fix. Add a viewport meta tag set to width=device-width and initial-scale=1, then audit your largest blocks at mobile widths.
- Page speed signals0.1s · 139 KBWhy this matters
Why it matters. Page weight and response time directly feed Core Web Vitals. Slow LCP and oversized HTML hurt rankings more than people expect.
Passing looks like. First-byte under 1.5s, HTML payload under 500 KB, fewer than 30 images on the initial render.
Fix. Trim render-blocking scripts, defer non-critical CSS, and serve compressed images sized to the viewport. Move heavy components below the fold.
- Schema markup2 schema blocksWhy this matters
Why it matters. JSON-LD structured data is how you earn rich results: review stars, FAQ accordions, breadcrumbs, article cards. Skip it and Google has nothing structured to pull from when it builds your SERP card.
Passing looks like. At least one valid JSON-LD block matching schema.org types relevant to the page (Article, Product, FAQPage, Organization).
Fix. Add an application/ld+json script block describing the page. Validate with Google's Rich Results Test before deploying.
- Broken links0/5 broken in sampleWhy this matters
Why it matters. Broken internal links waste crawl budget, degrade UX, and signal to Google that the site isn't well-maintained. They also cap how deep crawlers reach.
Passing looks like. Every internal link in the sample returns 2xx or 3xx. No dead anchors, no stale paths.
Fix. Use the link list above to spot the broken paths. Either restore the missing pages or update the links to point at live URLs.
- Image alt textNo imagesWhy this matters
Why it matters. Alt text is what screen readers read aloud, and what Google reads instead of pixels. Skip it and you lose on both fronts.
Passing looks like. Every meaningful image has a descriptive alt attribute. Decorative images can use alt="" to be skipped intentionally.
Fix. Audit images in /assets and CMS uploads. Write alts that describe what's in the image, not what it links to.
Every H1, H2, and H3 we found on the page, in document order.
Show heading outline
- H1Real-Time APIfor Public Social Data
- H2Why Choose TwitterAPI.io?
- H2Trusted by Developers Worldwide
- H2Built for Scale, Priced for Everyone
- H2Frequently Asked Questions
- H3Lightning Fast
- H3Ridiculously Affordable
- H3Enterprise Reliable
- H3Global Infrastructure
- H3Real-time Streams
- H3Auto-scaling
We HEAD-check up to five internal links to spot broken paths quickly.
Show sampled links
- 200 · OKhttps://twitterapi.io/status
- 200 · OKhttps://twitterapi.io/refund-policy
- 200 · OKhttps://twitterapi.io/payment
- 200 · OKhttps://twitterapi.io/acceptable-use
- 200 · OKhttps://twitterapi.io/terms
Was this report useful?
Share this scan
Every CrawlRanker scan gets a public, shareable URL. Send it to a client, post it in a thread, or benchmark a competitor.
Preview scan. SEO checks are live. AI scoring is in beta.