| Field | Value |
|---|---|
| Domain | getrundown.xyz |
| Category | YouTube niche intelligence and automated video summarization |
| Platform | Web |
| Pricing | $0, $7.99/month, and $15.99/month |
| Business model | SaaS subscription with free, Plus, and Max tiers |
| Pages crawled | 40 |
| Crawl date | 2026-10-23 |
Getrundown Review: strong product, mobile bottleneck (78/100)
Getrundown scores 78/100, with clear positioning for creators and strong technical SEO across the 40-page crawl. Its most material weakness is mobile performance, where the homepage LCP reached 11.2 seconds, while user guidance currently relies on an inline FAQ and feature pages.
Reviewed by SiteList Engine · 11 of 13 dimensions · published Reviewed on November 5, 2026
Is this your site?
Claim itQuick facts
- Pages crawled
- 40
- Crawl date
- 2026-10-23
- Platform
- Web
Executive summary
Getrundown's 78/100 reflects a product whose public story and technical foundation are stronger than its mobile delivery and self-serve guidance.
The strongest scores are Technical SEO at 94.1/100 and Risk & stability at 92.3/100. Usability scores 87.4, Audience & messaging 85.5, Writing quality 85.3, and First impressions & positioning 84.4, showing that the site explains the product and its audience clearly. Editorial QA also scores 80/100.
The main drag is Docs & self-serve help at 45/100, followed by Design execution at 64.1 and Performance at 67.2. The performance result is especially concrete on mobile: homepage LCP measured 11.2 seconds against a 2.5-second good threshold, while server response time was 9 milliseconds. Accessibility scores 75/100, with the primary URL field relying on a placeholder for its accessible name. The result is a legible, credible product story that needs a faster mobile entry point and fuller guidance for users after the homepage.
- Overall score
- 78/100
- Technical SEO
- 94.1/100
- Mobile homepage LCP
- 11.2 s
- Docs & self-serve help
- 45/100
01 · First impressions & positioning — a clear niche-intelligence promise, with illustrative proof
Rundown makes its category and primary audience legible immediately: the homepage label is "NICHE INTELLIGENCE FOR YOUTUBE CREATORS" and the H1 is "Know your niche before everyone else." Its strongest distinction is operational rather than generic summarization: it tracks channels, includes competitors, summarizes uploads, and delivers one brief. The FAQ sharpens that distinction against Eightify, Glasp, and Recall, which the site describes as one-video-at-a-time extensions. The proof surface is less developed. Product screenshots and Product Hunt and There’s An AI For That references support the story, but the testimonial block is explicitly "illustrative" and uses role-only labels such as "The tech reviewer." Add one named creator example with a measurable result beside the existing workflow proof.
- Hero category label
- NICHE INTELLIGENCE FOR YOUTUBE CREATORS
- Illustrative testimonial attribution
- The tech reviewer
02 · Audience & messaging — the trial and trust questions are answered before signup
Rundown covers the core evaluation path with unusual practical detail. The homepage offers a free summarization trial up to 10 minutes with no signup, while the FAQ states $0, $7.99/month, and $15.99/month tiers with usage limits. It also explains read-only YouTube access, the youtube.readonly scope, one-click disconnection, and what is outside the connection boundary. That makes offer comprehension strong. The remaining gap is attributable proof of the promised creator outcome: the homepage’s "How creators use it · illustrative" block uses role-only labels and supplies no named case study or measurable result. Keep creators primary in acquisition, then give the researcher and student routes separate proof rather than asking one message to carry all three jobs.
- No-signup trial
- Up to 10 min, no signup
- Plan prices
- $0, $7.99/month, and $15.99/month
- Google permission scope
- youtube.readonly
03 · Usability — three public paths are direct, but the app handoff remains unverified
The public information architecture supports the three tested goals without unnecessary detours. Product understanding follows the homepage to a relevant use-case page, conversion follows "Track my niche" to https://app.getrundown.xyz/, and content discovery follows "Blog" to a dated article list. The blog exposes titles, categories, summaries, dates, and "Read more" links in a consistent list; the sampled article is dated July 13, 2026. The supplied crawl stops at the external app boundary, so signup completion is not verified here. The clearest usability risk is the mobile front door: the homepage lab run records 11.2 seconds for both LCP and TTI. Preserve the current labels and routes while reducing the wait before the first action is ready.
- Conversion CTA
- Track my niche
- Blog article date
- July 13, 2026
- Mobile homepage LCP and TTI
- 11.2 s each
04 · Accessibility — the URL field needs a real name, landmarks, and contrast follow-up
The public pages have substantial accessible content, including 14 homepage images with no missing or empty alt attributes in the supplied DOM facts. The primary defect is the homepage URL form: the Paste a YouTube link… input has no visible label, aria-label, or aria-labelledby, so its placeholder is doing the naming work. The page also has no main landmark and no skip link. PSI reports contrast failures on the homepage, the sampled competitor article, and /summarize.html; the element-level pairs were not supplied, so selectors need a follow-up audit. Repair the input name, add a focus-visible skip link targeting main, correct the h2-to-h4 heading jump, then verify the computed accessibility tree.
- Homepage image alt coverage
- 14 images; no missing or empty alt attributes
- Primary URL field
- Placeholder only: Paste a YouTube link…
- Homepage accessibility score
- 83
05 · Design execution — an editorial system held back by small mobile controls
Rundown’s visual direction is distinctive and coherent: the homepage moves from hero to product proof, use cases, pricing, and FAQ, while the 390px capture preserves the sequence without horizontal overflow. The execution gap is interaction scale. The mobile layout facts report 30 small tap targets on the homepage and 15 on /discover, including homepage controls at 34×36px and 24×24px. Increase the hit areas to 44×44px with 8px separation while keeping the glyphs compact. The stylesheet extraction also reports 174 colors, 40 font-size values, 23 radii, and 68 spacing values; these are token-discipline proxies, but consolidation would improve maintainability. PSI also flags unsized images and heading order, while measured CLS remains 0 mobile and 0.014 desktop.
- Small mobile tap targets
- 30 homepage; 15 /discover
- Example homepage controls
- 34×36px and 24×24px
- Extracted style counts
- 174 colors, 40 font sizes, 23 radii, 68 spacing values
06 · Performance — 11.2 s mobile LCP despite a 9 ms server response
The performance bottleneck is the browser’s mobile delivery path, not an evidenced backend delay. Homepage mobile LCP is 11.2 seconds against Google’s 2.5-second good threshold, while the measured server response is 9 milliseconds; desktop LCP is 2.1 seconds. The homepage network summary weighs 3,745 KB across 30 requests, and desktop PSI estimates 1,834 KiB of image-delivery savings plus 2,563 KiB of cache-lifetime savings. The inventory includes summary_seg0.png at 1,048,652 bytes, but the supplied evidence does not prove it is the LCP element. Capture the trace first, then optimize the confirmed resource, reserve image dimensions, lazy-load below-fold screenshots, and apply long immutable caching to hashed assets. No CrUX field data was returned, so this remains a lab verdict.
- Homepage mobile LCP
- 11,200.823 ms
- Homepage server response
- 9 ms
- Image-delivery savings estimate
- 1,834 KiB
07 · Writing quality — direct copy with small heading and metadata defects
Rundown’s copy is specific, readable, and well matched to creators, researchers, and students. The homepage H1, "Know your niche before everyone else," states the value clearly, and the copy grounds the workflow in channel uploads, timestamped key points, and "worth-watching" verdicts. Average sentence length stays at 13–15 words, and the supplied AI-tell check found zero throat-clearing clichés. The remaining issues are editorial hygiene rather than voice: blog articles can contain duplicate H1 elements, legal pages at terms.html, privacy.html, and refund.html lack meta descriptions, and the creators landing-page title is 66 characters. Keep one H1 for each article, add concise policy descriptions, and trim the long title without changing its intent.
- Average sentence length
- 13–15 words
- Legal pages missing meta descriptions
- terms.html, privacy.html, refund.html
- Creators page title length
- 66 characters
08 · Risk & stability — the 40-page surface is healthy, with concentrated search exposure
No active traffic-suppression defect is evidenced in the supplied scan. The sampled 40 URLs return 200, the verified sitemap contains 3,882 URLs, HTTP and www consolidate in one 301 hop, and the nonexistent probe returns 404. Raw and rendered word counts also match across principal sampled templates. The material resilience concern is concentration: the property centers on YouTube summaries and niche intelligence, so AI Overviews and featured-answer surfaces could reduce clicks even if rankings hold. That is exposure, not evidence of traffic loss; GSC, analytics, and a SERP sample were unavailable. The history is thin rather than alarming: Wayback returned two homepage snapshots, on 2026-05-06 and 2026-06-20, while 35.3% of sitemap lastmod values fall within the last 90 days. Establish a GSC and analytics baseline before attributing future changes.
- Sampled URL status
- 40 URLs return 200
- Verified sitemap size
- 3,882 URLs
- Wayback homepage snapshots
- 2026-05-06 and 2026-06-20
09 · Editorial QA of content — strong core publishing, uneven discover-page hygiene
Rundown’s core editorial system is disciplined: the homepage FAQPage schema matches visible content, blog and landing-page copy avoids generic throat-clearing, and the voice stays consistent across role-specific pages. The weaker layer is programmatic discovery. The /discover page has more than 60 images without alt attributes, app plan query parameters share the title Rundown: YouTube, summarized and description across the root, ?plan=plus, and ?plan=max variants, and one long global-navigation anchor is repeated 17 times. These are concrete maintenance issues, not a reason to change the editorial voice. Add descriptive thumbnail alt text, canonicalize or differentiate plan URLs, and shorten repeated anchors to labels such as "For Creators" or "For Researchers."
- Discover images without alt text
- Over 60
- Repeated navigation anchor
- 17 uses
- Shared app metadata
- Root, ?plan=plus, and ?plan=max
10 · Docs & self-serve help — a six-item FAQ is not yet a support system
Self-serve guidance is currently limited to the homepage FAQ and product feature pages. The FAQ does useful work: it covers data privacy, youtube.readonly permissions, and billing tiers, and its FAQPage JSON-LD is machine-readable. The /llms.txt probe returns 404, and no public changelog or release-notes path was found. Build a dedicated /help hub with setup, permission-scope, and digest-management guides first; then add a concise /llms.txt capability and privacy summary and a simple changelog so users can answer operational questions without relying on marketing pages.
- Documentation pages detected
- 0 across /docs, /help, /kb patterns or subdomains
- Homepage FAQ
- 6-item FAQ section
- llms.txt probe
- 404
11 · Technical SEO — crawlability and rendering are strong across 40 sampled pages
Rundown’s sampled technical foundation is healthy. robots.txt allows crawling and declares a sitemap containing 3,882 URLs; sampled main-domain pages return 200 with self-canonicals, while HTTP and www each consolidate to HTTPS in one 301 hop. Raw and rendered word counts match across homepage, use-case, blog, discover, and sampled video pages, reducing the risk of client-rendered content being missed. Homepage structured data includes Organization, SoftwareApplication, and FAQPage JSON-LD alongside visible content. The principal technical SEO weakness is mobile delivery: homepage LCP is 11.2 seconds in PSI versus 2.1 seconds on desktop. Sampled headers also do not show HSTS or X-Content-Type-Options: nosniff. Optimize the confirmed LCP resource, then verify those headers on representative templates; do not generalize beyond the 40-page sample.
- Verified sitemap
- 3,882 URLs
- HTTP/www consolidation
- One 301 hop to HTTPS
- Homepage LCP
- 11.2 s mobile; 2.1 s desktop
Verdict — 78/100: strong product, fixable mobile bottleneck
Getrundown makes its core proposition legible quickly: it monitors subscribed YouTube channels, summarizes new uploads, and delivers the result in a daily email. The site also performs well on technical SEO at 94.1/100 and risk & stability at 92.3/100, with sampled pages live and indexable, matching raw and rendered word counts, and supported by clean single-hop host redirects.
Three fixes would sharpen the product experience. First, reduce the mobile homepage LCP from 11.2 seconds; the 9-millisecond server response indicates the bottleneck is in the delivered page rather than initial server response. Second, build guidance beyond the inline homepage FAQ and feature landing pages, which is reflected in the 45/100 Docs & self-serve help score. Third, give the primary URL field a proper accessible name instead of relying on a placeholder.
Rundown is a good fit for creators tracking a YouTube niche and competitors, with researchers and students as secondary audiences.
- Risk & stability
- 92.3/100
- Server response time
- 9 ms
- Docs & self-serve help
- 45/100
Methodology & data notes
This 13-dimension review combines evidence from a 40-page crawl on 2026-10-23 with public dimension summaries, supplied DOM facts, simulated cognitive walkthroughs, lab performance measurements, editorial checks, and technical SEO checks covering robots.txt, the verified sitemap, sampled responses, canonicals, and host redirects. Product facts were taken from the current crawl's structured data and FAQ evidence.
Dimensions 12 · Decision-support surfaces and 13 · Review-content integrity were excluded as not applicable. Search Console enrichment was pending: GSC was not connected and no GSC access was available, so no Search Console findings are included. Pricing remained unknown in the crawl, so this review does not invent commercial terms.
Read How SiteList scores for the scoring framework and data notes.
- Review dimensions
- 13
- Excluded dimensions
- 12 and 13, not applicable
- GSC enrichment
- Not connected; no access
Questions buyers actually ask
What does Rundown do?
Rundown monitors subscribed YouTube channels, summarizes new uploads, delivers the summaries in one daily email, and keeps them archived and searchable.
Who is Rundown for?
The product is aimed at content creators tracking a YouTube niche and competitors, with secondary use for researchers and students.
What access does Rundown request from Google?
It requests read-only access to YouTube channel subscriptions through the youtube.readonly scope. It cannot post videos or comments, modify subscriptions or playlists, see watch history, or access Gmail, Drive, Calendar, or Photos.
How is Rundown different from a YouTube summarizer extension?
Extensions such as Eightify, Glasp, and Recall summarize one video at a time while you watch. Rundown monitors subscribed channels automatically, sends a daily email, and archives summaries for later search.
What does Rundown cost?
Rundown offers a $0 tier, a $7.99/month tier, and a $15.99/month tier.