DEV Community: Spark

The Indie Developer's Visibility Playbook: From Zero to Your First 100 Users

Spark — Tue, 29 Sep 2026 11:05:12 +0000

You shipped. Nobody cares. Not because the product is bad, but because 30,000+ SaaS products launch every year and yours is one drop in a fire hose.

Here is the 30-day sequence that gets you to 100 users with no audience, no budget, and no spamming. Seven steps, in order, because doing them out of order is how most launches waste their one good shot.

Heads up: Do not start at Product Hunt. It is an amplifier, not a foundation. Steps 1 to 5 are what it amplifies.

Step 1: Fix the foundation (Day 1)

Your landing page has five seconds to answer three questions: what does this do, who is it for, why now.

If it says "revolutionizing the paradigm of collaborative synergy" instead of "track your expenses in 30 seconds", you have already lost.

[ ] Tagline under 10 words, says what the product does
[ ] Screenshot or GIF above the fold
[ ] Pricing visible, even if it is free
[ ] CTA says "Get started free", not "Learn more"
[ ] Page loads in under 3 seconds
[ ] OG meta tags set, so shared links preview properly

Step 2: Directory submissions (Day 1-7)

The single highest-ROI activity for a new product. Over 30 legitimate directories, most free, ten minutes each. Every one is a backlink, a permanent listing, and exposure to people actively shopping.

Start high, work down:

Directory	DA	Why it matters
Hacker News (Show HN)	93	Technical audiences, if you have one
Product Hunt	91	The gold standard, but save it for Step 6
G2, Capterra	92, 90	B2B buyers with purchasing intent
Crunchbase	91	Credibility and investor visibility
AlternativeTo	82	Appear in "[competitor] alternatives" searches
Indie Hackers	67	The bootstrapped community
BetaList	65	Pre-launch products
SaaSHub	56	SaaS-focused, alternative positioning
DevHunt	45	Developer tools

Tip: Prepare logo, tagline, short and long descriptions and screenshots ONCE, then reuse them everywhere. The full list of 35 with character limits is in the directories guide.

Step 3: Write one genuinely useful article (Day 7-10)

Not a blog post about your product. An article that solves a problem your users have before they need you.

Find the problem they hit before your product is relevant
Write the guide that solves it
Mention your product once, where it is genuinely the answer
Publish on your site, cross-post to Dev.to and Hashnode

What that looks like by product type:

Scheduling tool: "How to manage client bookings without losing your mind"
Analytics tool: "The 5 metrics that actually matter for your SaaS"
Dev tool: "What I got wrong launching my first developer tool"
Marketing tool: "35 directories to submit your app to in 2026"

It works because Google indexes it, nobody feels sold to, people share useful things, and by the time a reader needs a tool like yours they have already seen your name.

Tip: Always set the canonical URL to YOUR site when cross-posting. Rewrite the intro slightly per platform and use platform-appropriate tags.

Step 4: The safe outreach (Day 10-14)

Do not cold email customers. Email the people who WRITE about tools like yours: newsletter authors, roundup bloggers, YouTube reviewers, podcast hosts.

Hi [name], I built [product] - [one sentence]. Free tier, no catch. Thought it might be useful for your readers. Here's the link: [link]. No pressure, just relevant to [specific thing they published]. Cheers.

Under 100 words. Five to ten per week, not fifty. Publishers want to discover tools, so there is no downside if they ignore you, and one mention in a 5,000-subscriber newsletter beats 500 cold emails.

Step 5: Participate without promoting (Day 14+)

The hardest part for builders: show up where your users are and do not talk about your product.

Answer questions genuinely, with no link in the answer
Put your URL in your profile, never in comments
Mention the product only when someone asks "what do you use for X?"

Reddit (r/SideProject, r/indiehackers, r/webdev), Indie Hackers, niche Discords, Quora. One helpful comment at 50 upvotes drives more qualified traffic through your profile than 100 promotional posts that get downvoted.

Step 6: The launch event (Day 21-30)

By now: 20-35 listings live, one article published, early users arriving, a few newsletter authors aware of you.

Now you launch on Product Hunt.

[ ] Tuesday to Thursday, 12:01am Pacific
[ ] 30-second demo GIF or video ready
[ ] Genuine maker comment explaining why you built it
[ ] Tagline at 60 characters or under
[ ] Early users nudged to look (never say "upvote")
[ ] Your whole day cleared to reply to comments

Heads up: One shot. You get one good Product Hunt launch per product, and spending it before Steps 1 to 5 are done is the most common way indie launches are wasted.

Step 7: Let the flywheel spin (Day 30+)

More backlinks means better ranking, which means more organic traffic, which means more users, which means more word-of-mouth, which means more backlinks.

Keep it turning: one useful article a month, listings refreshed with new screenshots, testimonials collected and shown, comparison articles written against your alternatives.

What to avoid

Spamming communities. You get banned and the stain follows the product for years
Buying reviews. Platforms detect them, and getting caught means permanent delisting
Paying for "growth hacking". $2-5K to do the afternoon described above
Launching on Product Hunt first. See Step 6
Comparing yourself to VC-funded competitors. You are not competing on ad spend, you are competing on being useful and findable

The realistic timeline

Week	Activity	Expected result
1	Directory submissions	5-20 visitors/day
2	First article published and cross-posted	50-500 views
2-3	Outreach to 10-15 authors	1-3 mentions, 100-1000 visitors
3-4	Product Hunt launch	200-2000 visitors on the day
Month 2	SEO compounds	10-50 organic visitors/day
Month 3	Directories + SEO + word-of-mouth	50-200 visitors/day

Conservative numbers. One article that travels can 10x them overnight.

The bottom line

No following, no ad budget, no influencer act. Just: a product that solves something, a clear landing page, 32 directory submissions (5 hours), one useful article (3 hours), a few emails to the right people (1 hour), and a well-timed launch.

Two to three weeks of part-time work. $0.

The hard part is not the execution. It is accepting that nobody owes you their attention, and acting accordingly.

Sellular is a free visibility toolkit for indie developers: 30+ directories pre-filled with the right character limits and submission times, plus a visibility score for what search engines and AI answer engines actually read.

Originally published at sellular.online.

Check your company accounts before Companies House does

Spark — Mon, 21 Sep 2026 16:31:27 +0000

Rejected filings are almost never fraud. They are arithmetic, and the letter arrives weeks after the deadline has gone.

Tool	Rating
DuckTax	4.0 / 5
FreeAgent	3.5 / 5
TinyTax	3.5 / 5
WeFile	2.5 / 5

Disclosure: I build DuckTax, so its rating here is an interested party's. I have tried to be straight about what the others do better, and where one of them is the right choice I have said so.

The short version

These four sit at different points of the same year. DuckTax is the last mile: enter your company number, it pulls your name, registered office, officers and the real filing deadline from Companies House, then validates a balance sheet built from seven figures. FreeAgent is full bookkeeping for people who want the ledger maintained continuously. TinyTax and WeFile are filing tools with an account and a subscription attached. For a dormant or micro-entity company, a full bookkeeping suite is overkill.

What actually separates them

The difference that decides it is where the arithmetic runs and what it checks. DuckTax does the calculation in your browser, so the figures never leave the machine. It validates against the rules that actually cause rejections rather than simply accepting what you type. It also explains what each number means in plain English. It covers Ireland, Australia and the United States, saying plainly when a country does not require public filing at all. The subscription tools submit what you give them and let Companies House find the problem.

What you get free

DuckTax is free to use, including the Companies House lookup and the validation, which is the part that prevents a rejection. FreeAgent's free route depends on your business bank account rather than being a plan you can choose. TinyTax and WeFile both charge annually, so the free tier is a preview of the form rather than a filing you can complete.

Who should pick what

A director of a micro-entity or dormant company should use DuckTax and check the figures before submitting anything. A business with staff, invoices and monthly reconciliation needs FreeAgent or an accountant. Someone who wants a guided form and does not mind paying yearly should look at TinyTax. WeFile suits a director who wants a person on live chat while filing.

Worth knowing

The bookkeeping suites assume you keep books all year. DuckTax assumes you have seven figures and a deadline, and it checks them in the browser.

Originally published at sellular.online.

Turn your app into a narrated demo without recording

Spark — Mon, 21 Sep 2026 16:28:06 +0000

Nobody enjoys re-recording a demo because one click went wrong. One of these three never asks you to click at all.

Tool	Rating
QuickPeek	4.5 / 5
Loom	3.5 / 5
Synthesia	3.5 / 5
Descript	2.5 / 5

Disclosure: I build QuickPeek, so its rating here is an interested party's. I have tried to be straight about what the others do better, and where one of them is the right choice I have said so.

The short version

All three end with a video, and they get there in completely different ways. QuickPeek walks through your product, captures the run and narrates it, so the demo is generated rather than performed. Loom is the screen recorder everyone already knows, which means a retake every time you fumble a step. Synthesia builds a polished avatar reading a script, which is lovely for a training module and strange for a product walkthrough. Retakes are the real cost here, and only one of the three removes them.

What actually separates them

The split is whether an AI assistant can produce the video or only help you plan it. QuickPeek ships MCP tools, so an assistant lists what a demo can cover, generates one from a script, picks the voice. Opens the result in an editor for a trim. That turns a demo into something you ask for between two other tasks. The screen recorder still needs your hands and your voice, on the day, in one take.

What you get free

QuickPeek and Loom both have a free tier you can live on for a while. QuickPeek's covers real generated demos rather than a watermarked sample. Loom's free plan caps recording length and the number of videos you keep. Synthesia's free route is a short trial video, which is enough to judge the avatars and not enough to ship with.

Who should pick what

Someone shipping an app who needs a demo on the landing page today should pick QuickPeek. A person explaining a bug to a colleague in two minutes should open Loom and stop reading here. A team producing training modules in eight languages should pick Synthesia. Anyone who dreads hearing their own voice on a recording has one obvious option of the three.

Worth knowing

Loom records you doing it. Synthesia builds a presenter. QuickPeek drives the app itself and narrates what it did.

Originally published at sellular.online.

Get your app found without learning SEO first

Spark — Mon, 21 Sep 2026 16:13:34 +0000

The audit tools all grade your page. Only one of them will go and submit it to thirty directories while you watch.

Tool	Rating
Sellular	4.5 / 5
Semrush	4.5 / 5
SEOptimer	2.5 / 5
SE Ranking	3.5 / 5

Disclosure: I build Sellular, so treat its rating as the opinion of an interested party. I have tried to be straight about what the other three genuinely do better, and where they are the right choice I have said so.

The short version

All four tell you why a page is invisible to search. The difference is what happens next. Sellular carries a directory kit, a submission tracker and a badge, so the finding turns into a listing. Semrush and SE Ranking are research suites built for agencies reporting to clients, and both are overkill for one person with one app. SEOptimer sits in the middle: a fast audit, a tidy PDF, and nothing that follows through.

What actually separates them

The split is whether an AI assistant can do the work or only read about it. Sellular ships MCP tools, so an assistant scans a domain, pulls the visibility score, checks a product is ready to submit, records each directory submission as it lands. Generates the llms.txt file that tells other assistants what your product is. That turns a Saturday of copying the same tagline into thirty forms into a conversation. The audit suites hand back a report and leave the doing to you.

What you get free

All four let you start for nothing, but they give away different things. Sellular's free tier covers the audit, the directory kit and one tracked product. Semrush and SE Ranking cap free accounts at a handful of daily lookups, which runs out in an afternoon. SEOptimer's free audit is a single page report with the fixes behind the paid plan.

Who should pick what

Someone shipping their own app and dreading the launch admin should pick Sellular and let the assistant file the listings. An agency reporting rankings to ten clients every month should pick Semrush. A freelancer who sells audits as a deliverable should pick SEOptimer for the white label reports. SE Ranking suits a small agency that wants most of Semrush for less.

Worth knowing

The incumbents audit and report. Sellular audits, then does the submitting, and an assistant can drive the whole thing without you opening the dashboard.

Originally published at sellular.online.

The Indie Dev Visibility Playbook: From Zero Users to Your First 100

Spark — Sun, 20 Sep 2026 22:08:44 +0000

You shipped. Congratulations. Now comes the part nobody warned you about: nobody cares.

Not because your product is bad. Because the internet is a fire hose and you're a single drop. There are 30,000+ SaaS products launched every year. Most die in obscurity - not because they aren't good, but because their builders assumed the product would sell itself.

It won't. Here's what will actually get you from zero to your first 100 users without spending money, without an audience, and without being "that guy" who spams every community.

Step 1: Fix the foundation (Day 1)

Before you promote anything, make sure your house is in order.

Your landing page must answer three questions in 5 seconds:

What does this do?
Who is it for?
Why should I care right now?

If your homepage says "Revolutionizing the paradigm of collaborative synergy" instead of "Track your expenses in 30 seconds", you've already lost.

Check these:

[ ] Tagline is under 10 words and says what the product does
[ ] There's a screenshot or GIF above the fold
[ ] Pricing is visible (even if it's free)
[ ] There's a clear CTA button ("Get started free", not "Learn more")
[ ] The page loads in under 3 seconds
[ ] OG meta tags are set (so link previews look good when shared)

Step 2: Directory submissions (Day 1-7)

This is the single highest-ROI activity for a new product. Submit to app directories.

There are over 30 legitimate directories worth listing your product on, most of them free. Each submission takes 5-15 minutes and gives you:

A backlink (improves your Google ranking)
A permanent listing (drives traffic for years)
Exposure to active buyers

Start with the highest Domain Authority directories:

Product Hunt (DA 91) - the gold standard for launches
Hacker News Show HN (DA 93) - if you have a technical audience
G2 (DA 92), Capterra (DA 90) - B2B buyers with purchasing intent
Crunchbase (DA 91) - credibility and investor visibility
AlternativeTo (DA 82) - show up when people search "[competitor] alternatives"

Then work down to niche directories:

Indie Hackers (DA 67) - bootstrapped community
BetaList (DA 65) - pre-launch products
DevHunt (DA 45) - developer tools
SaaSHub (DA 56) - SaaS-focused

Prepare your assets once (logo, tagline, short description, long description, screenshots) and reuse them everywhere. A directory submission tool can pre-fill these for you.

Step 3: Write one genuinely useful article (Day 7-10)

Not a blog post about your product. An article that solves a problem your target users have.

The formula:

Think about what problem your users face BEFORE they need your product
Write a genuinely helpful guide solving that problem
Mention your product once, naturally, where it's relevant
Publish it on your own site AND cross-post to Dev.to, Hashnode, or Medium

Examples by product type:

Built a scheduling tool? Write "How to manage client bookings without losing your mind"
Built an analytics tool? Write "The 5 metrics that actually matter for your SaaS"
Built a dev tool? Write "X mistakes I made launching my first developer tool"
Built a marketing tool? Write "35 directories to submit your app to in 2026"

Why this works:

Google indexes it (long-term organic traffic)
It's not a sales pitch, so nobody feels sold to
People share useful content naturally
When readers need a tool like yours, they've already seen your name

Cross-posting rules:

Always set the canonical URL to YOUR site (this tells Google where the original lives)
Slightly rewrite the intro for each platform
Add platform-appropriate tags

Step 4: The safe outreach (Day 10-14)

You don't need to cold email potential customers. Email people who WRITE about tools like yours.

Who to contact:

Newsletter authors who cover indie dev tools
Bloggers who write "best tools for X" roundups
YouTube creators who review dev tools
Podcast hosts who interview indie founders

What to say (under 100 words):

Hi [name], I built [product] - [one sentence what it does]. Free tier, no catch. Thought it might be useful for your readers/viewers. Here's the link: [link]. No pressure, just thought it was relevant to [specific piece of their content you reference]. Cheers.

Why this is safe:

You're reaching out to PUBLISHERS, not random people
Publishers WANT to discover new tools to write about
One mention in a newsletter with 5,000 subscribers beats 500 cold emails
If they ignore you, no harm done - no public backlash

Send 5-10 of these per week. Not 50.

Step 5: Participate without promoting (Day 14+)

This is the hardest part for builders. You need to show up in communities and NOT talk about your product.

The rules:

Find communities where your target users hang out
Answer questions genuinely (no links to your product in the answer)
Put your product URL in your BIO/profile, not in comments
Only mention your product when someone explicitly asks "what tools do you use for X?"

Where to show up:

Reddit (relevant subreddits - r/SideProject, r/indiehackers, r/webdev, etc.)
Indie Hackers forums
Discord communities for your niche
Quora (answer questions related to your domain)

The math: One genuinely helpful Reddit comment that gets 50 upvotes drives more qualified traffic (from people clicking your profile) than 100 promotional posts that get downvoted.

Step 6: The launch event (Day 21-30)

By now you should have:

20-35 directory listings live
At least one article published and cross-posted
Some early users from directory traffic
A few newsletter authors aware of your product

NOW you launch on Product Hunt.

Product Hunt launch checklist:

[ ] Launch Tuesday-Thursday at 12:01 AM Pacific
[ ] Have a 30-second demo GIF or video
[ ] Write a genuine "maker comment" explaining why you built it
[ ] Prepare a one-line tagline (60 chars max)
[ ] Ask early users to check it out on launch day (don't say "upvote")
[ ] Be available ALL DAY to respond to comments

One shot. You get one good Product Hunt launch per product. Don't waste it before you have your foundation in place.

Step 7: Let the flywheel spin (Day 30+)

After 30 days, you should have:

Backlinks from over 30 directories improving your Google ranking
At least one article driving organic search traffic
Some early users and maybe a few paying customers
A Product Hunt launch giving you a traffic spike

Now the flywheel kicks in:

More backlinks = better Google ranking
Better ranking = more organic traffic
More traffic = more users
More users = more word-of-mouth
More word-of-mouth = more backlinks

Keep the flywheel going by:

Publishing one useful article per month
Updating your directory listings with new features/screenshots
Collecting and showcasing user testimonials
Writing comparison articles (your product vs. alternatives)

What to avoid

Don't spam communities. You'll get banned, and the stain follows you. One bad reputation incident can haunt an indie product for years.
Don't buy fake reviews. Platforms detect them. Getting caught means permanent delisting.
Don't pay for "PR" or "growth hacking" services. Most charge $2-5K and do exactly what you can do yourself for free.
Don't launch on Product Hunt first. Build your foundation first. PH is an amplifier, not a foundation.
Don't compare yourself to VC-funded competitors. You're not competing on ad spend. You're competing on being genuinely useful and easy to find.

The realistic timeline

Week	Activity	Expected result
1	Directory submissions (all 35)	5-20 visitors/day from directory traffic
2	Publish + cross-post first article	Additional 50-500 views depending on platform
2-3	Outreach to 10-15 newsletter authors	1-3 mentions = 100-1000 visitors
3-4	Product Hunt launch	200-2000 visitors on launch day
Month 2	SEO starts compounding	10-50 organic visitors/day
Month 3	Directory + SEO + word-of-mouth	50-200 visitors/day

These are conservative numbers. One viral Dev.to article can 10x these figures overnight.

The bottom line

Getting your first 100 users doesn't require a following, an ad budget, or being an influencer. It requires:

A product that actually solves a problem
A clear landing page
35 directory submissions (6 hours of work)
One genuinely useful article (3 hours of work)
A few emails to the right people (1 hour)
A well-timed Product Hunt launch (1 day)

Total time investment: roughly 2-3 weeks of part-time work. Total cost: $0.

The hardest part isn't the execution. It's accepting that nobody owes you their attention and acting accordingly.

Need help with directory submissions? Sellular is a free visibility toolkit that helps indie developers submit to over 30 curated directories with pre-filled forms, domain authority scores, and optimal submission timing.

Originally published at sellular.online.

12 Free Tools Every Indie Developer Needs for Marketing (2026)

Spark — Sun, 20 Sep 2026 22:06:11 +0000

You are a developer, not a marketer. You would rather write code than write ad copy. The problem is that a great product with no distribution loses to a mediocre one with some. Every time.

Every tool below is free to start. Eight of the twelve I built myself, because I ship a lot of small products and none of the free options did the job without a watermark or a subscription. They are marked, so you can weigh that however you like. The other four are free because their owners can afford it.

Make the assets (before you promote anything)

Every directory, store page and launch post wants the same five things: an icon, screenshots, a short description, a long one, and a demo video. Make them once.

PicLet

Remove backgrounds, replace colours, add borders, generate icons and store assets. Nothing is uploaded, so it runs on your machine and your unreleased screenshots stay there.

Use it for: app icons at every size a store asks for, and the 1366x768 screenshots the B2B directories insist on. Free, no account. piclet.app (mine)

QuickPeek

Turn any website into a demo video with AI narration, smooth animations and correct timing, in under two minutes. Point it at your own URL and it writes the walkthrough.

Use it for: the videoUrl field that Product Hunt, G2 and Capterra all have and most indie listings leave empty. Free tier. quickpeek.co (mine)

Vidlet

Auto-captions, compression, voice cleanup and 15+ other video tools. Nothing leaves your device. It is the CapCut replacement for people who do not want a subscription.

Use it for: cutting the QuickPeek demo into vertical shorts with burnt-in captions, which is the only format that travels on TikTok, Reels and YouTube Shorts. Free. vidlet.app (mine)

Canva

For the one job the above do not: a poster, a carousel, an OG image with real typography.

Free tier: 250,000+ templates and 5GB storage. canva.com

Get found

Sellular

Pre-fills your app across 30+ curated directories with each one's character limits, screenshot dimensions and best submission time, and scores your site on the 18 signals search engines and AI answer engines actually read.

Use it for: the single highest-ROI afternoon available to a new product. Every listing is a permanent backlink. Free tier: 5 listings, Chrome auto-fill, visitor analytics, plus Roast My Landing Page (paste a URL, get a Lighthouse-backed critique, no signup) and an auto-updating visibility badge for your README. sellular.online (mine)

Dev.to

A million developers, and Google indexes it within a day. Cross-post your articles here with canonical_url pointing back at your site, so the SEO credit goes home.

Free. There is no paid tier for writers. dev.to

Hashnode

A second developer audience for the same article, with the same canonical trick.

Read this before you rely on it: I cross-posted these three guides there and its auto-moderation archived all three inside an hour, with a note saying marketing-shaped writing is discouraged on free *.hashnode.dev subdomains and pointing at Hashnode Pro. Dev.to took the identical text without a murmur. Treat Hashnode as a bonus, not a plan.

Free tier: blog, newsletter, analytics. The custom domain is Pro. hashnode.com

Keep the drum beating

Viral Cat

Finds content worth posting and auto-posts to YouTube, TikTok, Instagram and four more platforms on a schedule.

Use it for: the follow-through nobody manages by hand. One demo video becomes six weeks of posts. Free tier. viral-cat.com (mine)

Bottled

Professional email on your own domain, with an API when you need one. Start collecting addresses on day one: it is the only channel you own.

Free to start. bottled.email (mine)

Google Search Console

Shows which searches already almost rank you, position 8 to 20. That list is your content calendar; you do not need keyword research beyond it.

Free. search.google.com/search-console

When it works, be ready

SparkStack

The full-stack Next.js starter I use for every one of these. Auth, database, payments and SEO wired up, so the next product starts at the interesting part.

Free and open. sparkstack.dev (mine)

SparkPay

Checkout, subscriptions, invoices, webhooks, coupons and referrals, with no Stripe SDK in your code. One deploy covers every app you own.

Use it for: the day someone actually wants to pay you, which is a bad day to start reading payment docs. sparkpay.dev (mine)

The order to do it in

Assets with PicLet, QuickPeek and Vidlet. One afternoon.
Submit to 30+ directories with Sellular. Another afternoon, and the backlinks compound for years.
Write one genuinely useful article, publish on your own site, cross-post to Dev.to and Hashnode with the canonical set.
Schedule the demo clips through Viral Cat so you are not posting manually at midnight.
Measure in Search Console, and write the next article about whatever sits at position 11.

Total cost: nothing. Total time: about a week of evenings.

What is deliberately not on this list

Social schedulers you pay for. You have no audience yet. Fix discovery first.
Paid ads. Not until you know which page converts. You will burn the budget learning targeting.
PR and growth-hacking retainers. They charge thousands to do the afternoon described above.
CRMs. A spreadsheet is fine until you have more leads than rows you can read.
AI article generators. They write forgettable prose that ranks like it. Write from what you actually shipped.

Sellular is a free visibility toolkit for indie developers: 30+ directories pre-filled, AI competitor reviews, and a visibility score that checks what search engines and AI answer engines read.

Originally published at sellular.online.

35 Best Directories to Submit Your App in 2026 (With Domain Authority Scores)

Spark — Sun, 20 Sep 2026 22:01:34 +0000

You built something great. Now nobody knows it exists.

That's the reality for most indie developers. You spend months building, ship a solid product, and then realize that "build it and they will come" is the biggest lie in tech.

Directory submissions are the lowest-effort, highest-ROI marketing activity for indie devs. Each submission takes 5-15 minutes, gives you a backlink (some dofollow from DA 90+ sites), and puts your product in front of buyers who are actively looking for tools like yours.

I've compiled every directory worth submitting to in 2026, ranked by Domain Authority. DA matters because higher-DA backlinks signal Google that your site is legitimate, which improves your own search rankings over time.

Tier 1: The heavyweights (DA 80+)

These directories have massive organic traffic and carry real SEO weight. Submit here first.

1. Hacker News - Show HN (DA 93)

URL: news.ycombinator.com/submit
Best time: Monday-Friday, 8-10 AM ET
Format: Title must be "Show HN: [Name] - [Tagline]" (80 char limit)
Tips: No logo upload. Text post optional but recommended. Dev-focused audience that values technical depth over polish. Don't post the same product twice unless it's substantially different.

2. Product Hunt (DA 91)

URL: producthunt.com/launch
Best time: Tuesday-Thursday, 12:01 AM PT
Format: Name, tagline (60 chars), description (260 chars), logo, screenshots, optional video
Tips: GIFs in the gallery get significantly more engagement than static images. Add a Loom or YouTube demo link. You get ONE good launch per product - don't waste it before you're ready.

3. Crunchbase (DA 91)

URL: crunchbase.com/add-new
Best time: Weekdays
Format: Name, URL, description (500 chars), logo, category
Tips: Free basic profile. High-authority dofollow backlink. Useful for credibility even if you're a solo founder. Add milestones and team info to look established.

4. G2 (DA 92)

URL: sell.g2.com/create-a-profile
Best time: Weekdays (3-5 business day review)
Format: Name, URL, description (500 chars), logo, category, pricing, screenshots (1366x768)
Tips: Reviews are heavily weighted in rankings. Once listed, actively collect user reviews. Gartner-owned, high buyer intent traffic.

5. Capterra (DA 90)

URL: capterra.com/vendors/
Best time: Weekdays
Format: Name, URL, description (1000 chars), logo, category, pricing, screenshots (1366x768), video URL
Tips: Also Gartner-owned. Free basic listing. Add a YouTube demo link for better visibility. B2B buyers use this for shortlisting.

6. SourceForge (DA 88)

URL: sourceforge.net/software/vendors/new
Best time: Weekdays
Format: Name, URL, description (1000 chars), logo, category, screenshots (1280x720)
Tips: Legacy platform but massive DA. Great purely for the SEO backlink. B2B discovery traffic is a bonus.

7. AlternativeTo (DA 82)

URL: alternativeto.net (sign in first, then use the site's own "Add application" flow)
Best time: Weekdays, EU/US daytime
Format: Name, URL, description (500 chars), category, tags
Tips: Community-driven, and submission requires a free account, so there is no direct submit link to bookmark. The real power move is adding your product as an alternative to popular competitors. You show up whenever someone searches "[competitor] alternatives".

8. GetApp (DA 82)

URL: getapp.com/vendors/
Best time: Weekdays
Format: Name, URL, description (1000 chars), logo, category, pricing
Tips: Another Gartner property. Free basic listing. Moderated.

Tier 2: Strong directories (DA 50-79)

Good traffic, solid backlinks, and engaged audiences. These compound over time.

9. Wellfound / AngelList (DA 75)

URL: wellfound.com/recruit/overview
Best time: Weekdays, US hours
Format: Name, URL, tagline (80 chars), description (500 chars), logo, category
Tips: Strong dofollow backlink. Company profile doubles as a hiring page.

10. StackShare (DA 72)

URL: stackshare.io/vendors
Best time: Tuesday-Thursday, US business hours
Format: Name, URL, description (300 chars), logo, category
Tips: Best for developer tools and infrastructure. Claim your listing via the vendor portal.

11. TrustRadius (DA 72)

URL: trustradius.com/vendors
Best time: Weekdays
Format: Name, URL, description (1000 chars), logo, category, pricing, screenshots (1366x768)
Tips: B2B buyer trust platform. Reviews are gated and verified, which means they carry more weight than open platforms.

12. Indie Hackers (DA 67)

URL: indiehackers.com/products/new
Best time: Weekdays, US hours
Format: Name, URL, tagline (80 chars), description (500 chars)
Tips: THE community for bootstrapped products. Post revenue milestones and updates as separate posts to stay visible. Community engagement matters.

13. Slant (DA 66) - down

URL: ~~slant.co/improve~~
Status: The origin server has been unreachable behind Cloudflare (error 526) since September 2026. Nothing to submit to while that lasts. It was comparison-focused, so AlternativeTo below fills the same slot.

14. BetaList (DA 65)

URL: betalist.com/submit
Best time: Monday-Wednesday morning
Format: Name, URL, tagline (60 chars), description (300 chars), logo, category
Tips: Best for pre-launch or beta products. Free queue takes 2-3 weeks. $129 fast-track option. Great for building an early waitlist.

15. GoodFirms (DA 64)

URL: goodfirms.co/add-product
Best time: Weekdays
Format: Name, URL, description (500 chars), logo, category, pricing
Tips: B2B software review platform. Free listing with moderation. Good for lead generation from buyer-intent searches.

16. There's An AI For That (DA 62)

URL: theresanaiforthat.com/get-featured/
Best time: Weekdays, morning US
Format: Name, URL, tagline (80 chars), description (300 chars), category, pricing
Tips: Largest AI directory. Only relevant if your product has AI features. Paid submission ($347) or free via their monthly thread.

17. Futurepedia (DA 58) - paid only

URL: futurepedia.io/submit-tool
Status: Not a free listing. The submission page reads as an ordinary sign-in-gated form and is not one: when it was last measured the tiers were $247 basic (sold out) and $497 verified. Check the current figure on their own page before paying, and treat any free-submission write-up as out of date.
Tips: AI tools directory with 400K+ monthly visitors, so it may be worth the spend if your product is AI-related. It is excluded from the Sellular kit for this reason, so nothing here will pre-fill it.

18. SaaSHub (DA 56)

URL: saashub.com/services/submit
Best time: Weekdays, morning US
Format: Name, URL, tagline (80 chars), description (500 chars), logo, category, pricing
Tips: SaaS-focused. Good for "alternative to" positioning. Free listing.

19. Startup Stash (DA 55)

URL: startupstash.com/add-listing/
Best time: Weekdays
Format: Name, URL, description (500 chars), logo, category, pricing
Tips: Curated directory of startup resources and tools. Free listing.

20. Toolify.ai (DA 55)

URL: toolify.ai/submit
Best time: Weekdays, morning US/EU
Format: Name, URL, tagline (80 chars), description (500 chars), logo, category, pricing
Tips: One of the largest AI directories with 500K+ monthly visitors. Free submission with editorial review. Only for AI products.

21. Software Suggest (DA 55)

URL: softwaresuggest.com/vendors
Best time: Weekdays
Format: Name, URL, description (500 chars), logo, category, pricing
Tips: B2B software discovery with buyer-intent traffic. Free vendor listing.

22. AlternativeMe (DA 52)

URL: alternative.me/how-to/submit-software/
Best time: Weekdays
Format: Name, URL, description (500 chars), category
Tips: Similar to AlternativeTo. Position your product against competitors to appear in comparison searches.

23. SaaSWorthy (DA 51)

URL: saasworthy.com/offerings
Best time: Weekdays
Format: Name, URL, description (500 chars), logo, category, pricing
Tips: Free listing. Moderated. Keep your profile updated.

Tier 3: Indie and niche directories (DA 30-49)

Smaller audiences but highly targeted. These are YOUR people - indie devs, builders, hackers.

24. DevHunt (DA 45)

URL: devhunt.org
Best time: Monday-Thursday, morning US/EU
Format: Name, URL, tagline (60 chars), description (300 chars), logo
Tips: Dev tools launchpad. Requires GitHub login. Submissions via GitHub PR. Community voting. Relaunch allowed for major updates.

25. SideProjectors (DA 45)

URL: sideprojectors.com/project/submit
Best time: Weekdays, morning US
Format: Name, URL, tagline (100 chars), description (1000 chars), logo, category
Tips: Also a marketplace for buying/selling side projects. Account required.

26. OpenAlternative (DA 42)

URL: openalternative.co/submit
Best time: Weekdays
Format: Name, URL, description (300 chars), category
Tips: Open-source alternative directory. Best if your product is open source or has a generous free tier. Dev-focused.

27. LaunchingNext (DA 42)

URL: launchingnext.com/submit/
Best time: Monday-Wednesday
Format: Name, URL, tagline (80 chars), description (500 chars), logo, category
Tips: Free submission. Startup-focused. Moderated.

28. PitchWall (DA 41)

URL: pitchwall.co/submit
Best time: Monday-Wednesday, morning
Format: Name, URL, tagline (60 chars), description (400 chars), logo, category
Tips: Free submission. Beta/early-stage focused. Good for very early products.

29. Uneed (DA 40)

URL: uneed.best/submit-a-tool
Best time: Early week for best exposure
Format: Name, URL, tagline (60 chars), description (300 chars), logo
Tips: Daily launches. Free queue or $29.99 to skip. Includes a DR 74 dofollow backlink and exposure to 11K newsletter subscribers.

30. ToolFinder (DA 38)

URL: toolfinder.com/submit
Best time: Weekdays, morning US
Format: Name, URL, tagline (80 chars), description (300 chars), logo, category, pricing
Tips: AI and SaaS tool directory. Free listing.

31. Launched (DA 36) - defunct

URL: ~~launched.io/SubmitStartup~~
Status: The domain no longer resolves as of August 2026. Skip it and spend the slot on Uneed or MicroLaunch instead.

32. StartupBuffer (DA 35)

URL: startupbuffer.com/site/submit
Best time: Monday-Wednesday
Format: Name, URL, tagline (80 chars), description (500 chars), logo
Tips: Free submission. Startup-focused.

33. MicroLaunch (DA 35)

URL: microlaunch.net/premium
Best time: Monday-Wednesday for community votes
Format: Name, URL, tagline (60 chars), description (300 chars), logo
Tips: Indie-focused micro launches. Community voting. Premium option available.

34. Fazier (DA 35)

URL: fazier.com/submit
Best time: Monday-Thursday
Format: Name, URL, tagline (60 chars), description (300 chars), logo
Tips: Product Hunt alternative with a growing community. Free launch with upvoting system.

35. 1000.tools (DA 30) - down

URL: ~~1000.tools/my/tools/create~~
Status: The site removed its submission path (404) and no submit link remains on the homepage, as of September 2026. Spend the slot on Uneed or Fazier instead.

The submission strategy

Don't just blast all 35 in one afternoon. Here's the order that maximizes impact:

Week 1: Tier 1 directories (DA 80+). These take the longest to approve but carry the most SEO weight.

Week 2: Tier 2 directories (DA 50-79). Good balance of authority and speed.

Week 3: Tier 3 directories (DA 30-49). Fast approvals, targeted audiences.

After submission: Track which directories actually send traffic. Double down on those. Update your listings monthly with fresh screenshots, updated descriptions, and new features.

What you'll need before you start

Prepare these assets once and reuse them across all 35:

App name and URL
Tagline (keep it under 60 characters for maximum compatibility)
Short description (300 characters - fits every directory)
Long description (500-1000 characters - for directories that allow it)
Logo (square, at least 512x512px, PNG with transparent background)
Screenshots (1366x768 for B2B directories, 1270x760 for Product Hunt)
Demo video URL (YouTube or Loom, under 2 minutes)
Pricing info (even if it's "Free with paid plans")
Category tags (SaaS, Developer Tools, Marketing, AI)

Or use a directory submission tool like Sellular that pre-fills these fields across every directory in its catalogue and tells you exactly what each one requires.

The math

Three of the 35 above are down, so 32 are actually submittable. Average submission
time: 10 minutes each. Total time: roughly 5 hours.

In exchange, you get:

32 backlinks (some dofollow from DA 90+ sites)
Permanent listings that drive traffic for years
SEO authority that improves your Google ranking for every page on your site
Direct exposure to millions of monthly visitors across these platforms

Five hours of work for years of compounding returns. There is no marketing activity with a better ROI for indie developers.

Have a product that needs visibility? Sellular is a free toolkit that helps indie developers submit to over 30 curated directories, the ones listed above among them, with pre-filled forms, character limits, and optimal submission timing built in.

Originally published at sellular.online.

NHS Jobs will not let you upload a CV, and that changes all the advice

Spark — Sun, 20 Sep 2026 17:21:09 +0000

If you are applying for a developer role at NHS England, an NHS trust, or through the Civil Service, the CV you spent a weekend polishing is not going to be read. Not because it is bad. Because there is nowhere to put it.

NHS Jobs states it in their own help article, in one sentence: "You cannot upload your CV to NHS Jobs service."

That page has been viewed just over six thousand times at the time of writing, which tells you roughly how many people discover this at the worst possible moment.

It is stricter than "no upload"

There is a second option that sounds like a reprieve and is not.

When an employer posts a vacancy, they can allow applicants to apply using an online application form or a "CV application". If they pick the CV route, you still do not attach a file. You copy and paste the contents of your CV into a mandatory section, next to these, which are required either way:

Contact details
Right to work status
Your CV, as typed text
Unspent criminal convictions and cautions
Guaranteed interview scheme questions

So the "CV application" is still a form. There is no path through NHS Jobs that accepts a document. Civil Service is a different system with the same shape of problem: Success Profiles, written statements of around 250 words per behaviour, frequently blind sifted so the reviewer sees neither your name nor your employer.

Why this breaks the advice you have been given

Nearly all job hunting advice aimed at developers assumes an applicant tracking system. Get the keywords in, keep the formatting machine readable, run it through a free checker, upload, move on. That advice is fine, and several of those checkers are genuinely good.

None of it applies here. These applications are scored by a person against a published person specification, criterion by criterion.

What actually changes:

Keyword density does nothing. A human is checking whether you evidenced each listed criterion. Evidence, not vocabulary. Salting your application with terms from the advert is at best neutral and at worst reads as padding to someone who has sifted two hundred of these.

Your employer's name does nothing under a blind sift. "Senior engineer at a company you have heard of" is exactly as persuasive as the same sentence with the company removed, because the company is removed. Everything has to be carried by what you did.

The marking scheme is published in advance. That is the genuinely good news, and most applicants waste it. The person specification lists essential and desirable criteria. Answer them in the order they are printed and you have made the sifter's job trivial. Answer them in your own preferred order and you have made them hunt for points they are allowed to award you zero for not finding.

The real cost is retyping. Every trust runs its own recruitment. Apply to ten and you will type the same employment history, the same dates, the same referees, the same right to work answers into ten fresh sets of boxes. This is where the hours actually go, and it is not the interesting part of applying for a job.

What I built, and what it does not do

That last point is the one I could fix, so I did. Still Applying is mine, so treat it as disclosed: you enter your history once and a browser extension fills it into the application form you have open. It is triggered from the toolbar on whatever page you are on, rather than from a fixed list of supported career sites, which matters here because NHS trusts and Civil Service departments are exactly the sites that never appear on those lists.

Being straight about the limits, because in this context they are large:

It does not write your person specification evidence for you. That is the part that gets you sifted in, and it is yours.
It shows an ATS compatibility score, and on an NHS application that number is close to meaningless. It is scoring a CV, and as above, a CV is not the instrument being used. Ignore it here.

So the tool saves you the retyping. It does not save you the thinking, and any tool claiming otherwise for this particular process is selling you something.

The habit that is worth more than any of it: before you apply anywhere in the NHS, open the person specification and the application form side by side, and answer the criteria in the order they are printed. It costs nothing and almost nobody does it.

Enter your history once at stillapplying.com

Jake

You can ask Companies House for more time, but only until the day you are late

Spark — Sun, 20 Sep 2026 17:18:34 +0000

I run a UK limited company on my own, and I build small tools. One of those tools knew my filing deadline, knew exactly what missing it would cost, and never once mentioned the thing that would actually have helped. That omission is worth about £150, so here it is written down plainly.

The part everybody knows

Miss your Companies House accounts deadline and the penalty is automatic. No warning letter first, no discretion. The published scale for a private company:

How late	Penalty
Not more than 1 month	£150
More than 1 month, up to 3 months	£375
More than 3 months, up to 6 months	£750
More than 6 months	£1,500

And the one that catches people twice: the penalty doubles if you file late in two successive financial years.

The part almost nobody mentions

You can ask Companies House for more time. It is free, the application takes about fifteen minutes, and you do it on their own service.

But you have to apply before your filing deadline. From the gov.uk guidance, in their words: you must apply for the extension, or file your accounts, before your filing deadline, or you will receive a late filing penalty.

Read that again, because it is the entire point of this post. The window to ask for more time closes on exactly the day the penalty starts. There is no grace period in which you notice you are late and then apply. The moment you are late, the option you had is gone, permanently, for that set of accounts.

So the date that belongs in your calendar is not "file by 30 September". It is "by 30 September, either file or ask for more time", and those are two very different amounts of work. One is a year of bookkeeping. The other is a form.

Three things that get an application refused

Companies House is judging whether an event outside your control stopped you filing. The event is what is being assessed, not the inconvenience. Their own published examples are an unexpected illness, or a fire that destroyed the company records a few days before the deadline.

What goes wrong:

Ordinary delay dressed up as an emergency. This is the commonest refusal. Being busy, a client paying late, a bookkeeper being slow: none of these are events outside your control in the sense meant here.
A reason with no dates in it. If nobody can line your event up against your deadline, nobody can check that it caused anything.
Anything you could not evidence if they asked. Supporting documents are optional on the form. Being able to produce them is not.

There is a fourth mistake that is not about the form at all: do not down tools while you wait for a decision. Companies House tells you to carry on preparing the accounts regardless, and if the answer comes back no, you have burned the days you had left.

The ceiling no reason gets you past

The law caps the whole filing period at twelve months from your accounting reference date. If your period ended on 15 January, nothing later than 15 January the following year can be granted, however good your reason and however sympathetic the reviewer.

So the extension is real, but finite. If your deadline is already eleven months out from your period end, there is very little left to give you, and it is better to know that now than on the day you apply.

Where I ended up

The tool is Duck Tax, and it is mine, so take that as disclosed. It is a free micro-entity accounts checker: seven figures in, a validated FRS 105 balance sheet out, no account needed and nothing sent anywhere unless you ask for it. Its MCP server has a tool that answers the only question that matters on the day you find out, which is whether the extension window is still open and how many days are left in it.

Being precise about the limits, because this is exactly the area where vague marketing does real damage: it prepares an application, it cannot submit one, and it does not file accounts with anybody. A director makes the application on Companies House's own service, and the checked numbers go to whoever does your filing. None of this is accounting advice.

Honestly, if you take one thing from this post, let it be the calendar entry rather than the tool. Put the real date in: not the filing deadline, but the last day you can still ask for more time. They are the same day, and that is the problem.

Check your figures free at ducktax.com

Jake

Playwright on Vercel: four things Next.js file tracing will not do for you

Spark — Sun, 20 Sep 2026 17:16:14 +0000

I ship a tool that drives a real browser through a website and records a narrated demo video. Moving that from a CLI to a Next.js API route on Vercel took four separate fixes, and every one of them failed in a way that pointed somewhere else.

Writing them down in case it saves you the week it cost me.

1. process.env.VERCEL is not a runtime signal

Start here, because this is the one that will waste the most of your time.

The obvious way to choose between local Playwright and serverless chromium is to ask whether you are running on Vercel:

const isServerless = !!process.env.VERCEL;

That is wrong the moment anyone runs vercel env pull. It writes VERCEL=1 and VERCEL_ENV=production straight into .env.local, so your laptop now reads as production and takes the serverless path, against a chromium binary that is not there. Nothing about the failure points at your env file.

The variables that only exist inside the deployed function are the Lambda ones:

export type BrowserTarget = 'serverless' | 'local';

export function resolveBrowserTarget(
  env: Record<string, string | undefined> = process.env,
): BrowserTarget {
  if (env.QUICKPEEK_BROWSER === 'serverless') return 'serverless';
  if (env.QUICKPEEK_BROWSER === 'local') return 'local';
  // Set by the Lambda runtime Vercel functions execute in. Never present in a
  // pulled .env file, which is exactly why it is the one usable signal.
  return env.AWS_LAMBDA_FUNCTION_NAME || env.LAMBDA_TASK_ROOT
    ? 'serverless'
    : 'local';
}

Two things worth copying. It is a pure exported function, because getting this wrong is invisible until either production or local dev quietly stops working, and you want a test sitting on it. And the manual override exists so you can force either branch while you are debugging the other one.

2. The file tracer cannot see a dynamic import or an fs read

@sparticuz/chromium ships chromium as a brotli archive that it unpacks into /tmp on first use. You load it through a dynamic import, and it then reads its own payload off disk. Next's file tracer sees neither the require nor the file, so it packs your function without the binary. The route deploys cleanly and throws at launch.

You have to name it by hand, per route, because each API route becomes its own serverless function:

outputFileTracingIncludes: {
  '/api/record-video': ['./node_modules/@sparticuz/chromium/bin/**/*'],
  '/api/validate-plan': ['./node_modules/@sparticuz/chromium/bin/**/*'],
},

The same trap catches anything read with fs at runtime. Fonts and images used by OG image routes are the usual other victims.

3. Native packages have to be made external twice

serverExternalPackages keeps Node native packages out of the webpack bundle. Playwright pulls in electron and ws internals that break the build when bundled, and @sparticuz/chromium is a 67MB archive webpack must not touch:

serverExternalPackages: [
  '@sparticuz/chromium',
  'playwright',
  'playwright-core',
  'sharp',
],

That handles imports resolving inside node_modules. If you also depend on a local package by file: path, its internal imports resolve outside node_modules and slip past the list entirely. You need the escape hatch as well:

webpack: (config, { isServer }) => {
  if (isServer) {
    config.externals.push('playwright', 'playwright-core', '@sparticuz/chromium');
  }
  return config;
},

4. A file: dependency can make the build never finish

This one did not error, which is why it took longest. next build sat on "Creating an optimized production build" until I killed it, first at ten minutes, then at fifty five.

The cause: bun resolves a file:.. dependency by copying the whole directory into node_modules, and the files field in package.json does not restrict that copy the way npm pack would. So the copy contained web/, which contained node_modules, which contained another copy, roughly twelve levels deep. Next had also picked the repo root as its workspace because of a stray lockfile sitting up there, and was walking that whole tree.

One line:

outputFileTracingRoot: __dirname,

If a build hangs with no output at all, suspect file tracing walking somewhere enormous before you suspect anything else.

Two smaller ones at launch time

Do not pass headless: true. The args from @sparticuz/chromium already contain --headless='shell', quotes included, and Playwright appends its own switch on top, which leaves chromium holding two conflicting flags. The vendor's own Playwright example omits it for this reason.

const [{ default: serverless }, { chromium }] = await Promise.all([
  import('@sparticuz/chromium'),
  import('playwright-core'),
]);

const executablePath = await serverless.executablePath();
if (!executablePath) {
  throw new Error('Serverless chromium did not unpack, no executable path was returned');
}

return chromium.launch({
  ...options,
  executablePath,
  args: [...serverless.args, ...(options.args ?? [])],
});

Think twice before disabling the graphics stack to shave cold start time. Leaving it on costs about 1.6MB of extra unpack per cold start. Turning it off disables WebGL and canvas acceleration, which is the difference between recording a canvas based app and recording a blank rectangle.

What this is all for

The product is QuickPeek, which is mine, so treat that as disclosed: you give it a URL, it drives a real browser through your site, writes and speaks the narration, and cuts the result into a demo video with captions. Everything above is why that runs in a serverless function instead of on a machine I have to keep alive.

If you are putting Playwright behind a Next.js route, the ordering that actually worked was: get the target resolution honest first, then trace the binary in, then fight webpack. Doing it in any other order means debugging three problems wearing the same error message.

Point it at your own URL: quickpeek.co

Jake

My landing page had no hero. The HTML was correct the whole time.

Spark — Sun, 20 Sep 2026 11:48:45 +0000

I found this while taking screenshots for a Product Hunt listing, which is an embarrassing way to discover that the top of your own marketing site has been missing.

The page opened on its second section. The headline, the subheading, the platform badges, the animated terminal and the single call to action button were all absent. Not mispositioned. Absent.

Everything I would normally check said it was fine

This is the part worth writing down, because every instinct I reached for came back green.

curl returned the headline. It is right there in the served HTML:

curl -s https://example.dev | grep -o "Your Next Stack, Sparked"
# Your Next Stack, Sparked

The element existed in the DOM. It had real dimensions:

document.querySelector('h1').getBoundingClientRect()
// { x: 83, y: 336.9, width: 536, height: 48.4 }

No console errors. No failed requests. No hydration warning. A 536x48 heading, sitting at y=337, which is on screen.

So the markup was right, the element was right, the element had a size, and the element was invisible.

The measurement that actually found it

I stopped checking whether things existed and started measuring what the layout was doing. Specifically, the height of every direct child of the scroll container:

const sc = document.querySelector('div.flex-1.min-h-0.overflow-y-auto');
[...sc.children].map(e => ({
  tag: e.tagName,
  offsetTop: e.offsetTop,
  height: Math.round(e.getBoundingClientRect().height),
  text: e.textContent.trim().slice(0, 30),
}));

Which gave me this:

element	offsetTop	height
hero `<section>`	57	0
demo video `<section>`	57	654
features `<section>`	711	919

Two sections claiming the same offsetTop. The hero was zero pixels tall, so the next section laid out on top of it, and the hero's own overflow-hidden clipped its contents out of existence.

The h1 genuinely was 536x48. It was just 536x48 inside a box with no height, painted underneath the section that came after it.

Why it collapsed

The page shell is one viewport tall and never scrolls itself. A fixed-height flex column holds everything, and one inner div does the scrolling:

<div class="h-dvh overflow-hidden flex flex-col">
  <nav class="shrink-0">...</nav>
  <div class="flex-1 min-h-0 overflow-y-auto flex flex-col">
    <section class="relative overflow-hidden">...</section>  <!-- the hero -->
    <section>...</section>
    <section>...</section>
  </div>
</div>

Every section is a flex item in a fixed-height column, so every section is shrinkable. flex-shrink defaults to 1.

Normally that does not matter, because a flex item's automatic minimum size (min-height: auto) stops it shrinking below its content. That default is what keeps flex columns from crushing themselves.

But min-height: auto only applies when the item's overflow is visible. From the CSS Flexible Box spec: the automatic minimum size is zero when the box is a scroll container, and overflow: hidden makes it one.

The hero was the only section with overflow-hidden on it. So it was the only section whose minimum size was zero. Every other section held its ground, the column still needed to give up space, and the one item that could shrink to nothing did exactly that.

The overflow-hidden was there to clip a decorative background. It was not doing anything I would have thought of as layout.

Proving it before changing anything

Two one line experiments in the console on the live page, before I touched the source:

const hero = document.querySelector('div.flex-1.min-h-0.overflow-y-auto > section:first-child');
const h = () => Math.round(hero.getBoundingClientRect().height);

h();                                 // 0
hero.style.flexShrink = '0'; h();    // 716
hero.style.flexShrink = '';
hero.style.minHeight = 'auto'; h();  // 0

flex-shrink: 0 brings it back. min-height: auto does not, which is the tell: the automatic minimum is already being computed as zero because of the overflow, so restating it changes nothing. That second result is what turns a plausible theory into the actual mechanism.

The fix

One class.

- <section className="relative overflow-hidden">
+ <section className="relative shrink-0 overflow-hidden">

I left a comment on it, because the next person to tidy up a "redundant" utility class will delete it:

shrink-0 is load-bearing. This section is a flex item in the fixed-height
flex column above, so it is shrinkable by default. Every other section keeps
min-height: auto and resists, but overflow-hidden forces this one's automatic
minimum size to zero, so it absorbed the whole overflow and collapsed to 0px.
Do not remove without also removing overflow-hidden.

How to check your own

If you have a fixed-height flex column anywhere, measure the children rather than trusting that the content is present:

[...document.querySelectorAll('section, main > div')]
  .map(e => [e.className.slice(0, 40), Math.round(e.getBoundingClientRect().height)])
  .filter(([, h]) => h === 0);

Anything returning zero while containing real content is this bug. The combination to look for is a flex or grid item that sets overflow to anything other than visible, inside a container with a constrained height.

Worth saying plainly: none of my usual checks could have caught this. Server rendered HTML tests pass, because the HTML is correct. Snapshot tests pass, because the tree is correct. A smoke test asserting the headline is in the document passes. The only thing that catches it is asking the browser how tall the box actually is.

Disclosure

The site is SparkStack, a Next.js starter I sell, so this was my own shop window with the lights off. I do not know exactly how long it was broken, which is its own lesson: I had no check that would have told me. The fix is deployed and the hero has been back at 716 pixels since.

If you take one thing from this, make it the measurement rather than the fix. getBoundingClientRect().height on your layout wrappers costs nothing and tells you something that reading the markup cannot.

I checked 14 domains. None had ever submitted a sitemap.

Spark — Thu, 17 Sep 2026 08:52:53 +0000

I run fourteen small SaaS sites. Last week I went to check how they were doing in search and found something embarrassing: not one of them had ever had a sitemap submitted. Not to Google, not to Bing. Fourteen domains, 188 URLs, sitting there for months.

The annoying part is that every single site was doing the work correctly. Each served a valid sitemap.xml. Each declared it in robots.txt. The framework generated it automatically. Everything a tutorial tells you to do was done.

Nobody had pressed the last button.

Serving a sitemap is not submitting one

This is the gap I want to flag, because I suspect it is common.

A sitemap in robots.txt is a passive hint. A crawler that already visits your site will eventually find it. Submitting it in Search Console is an active declaration: here is the list, please read it now, and here is where I will tell you when it changes.

For a site with existing traffic the difference is small. For a new site with no inbound links, the passive route can mean waiting a long time to be discovered at all, because nothing is prompting a crawler to come in the first place.

Checking takes a minute per property:

Google: Search Console, Indexing, Sitemaps
Bing: Bing Webmaster Tools, Sitemaps

If the table is empty, that is the whole problem.

Bing matters more than its market share suggests

The reflex is to do Google and stop. That reflex is now out of date, for a reason that has nothing to do with how many people use Bing.

ChatGPT's browsing is built on Bing's index. If you care about being mentioned when somebody asks an assistant for a tool like yours, Bing is not the afterthought, it is the channel. Claude leans on Brave, which has its own submission form. Perplexity runs its own crawler.

So "SEO" quietly became several different indexes with different front doors. Submitting to Google alone covers fewer of them than it used to.

Bing was also the bigger miss in my case. One of my domains was not even registered in Bing Webmaster Tools, so its 30 URLs were invisible to that whole side of the map.

Two things that cost me time

A domain property rejects a bare path. In Google Search Console, if your property is a Domain property (sc-domain:example.com), the sitemap field will not accept sitemap.xml. It returns "Invalid sitemap address" with no hint as to why. It wants the full https://example.com/sitemap.xml. A URL-prefix property takes the bare path. Same field, same console, opposite requirement.

Deploy the verification file before you create the property. If you add a URL-prefix property and the verification file is already live, Google skips the verification step entirely and shows "Ownership auto verified". If you create the property first you get sent round a download-upload-verify loop instead.

Worth knowing: the Google HTML verification token is per account, not per site. The same googleXXXX.html file verifies every domain you own. Once you have it, adding a new site is one file and one click.

What I would check on your own projects

Open Search Console and Bing Webmaster Tools and look at the Sitemaps table. Empty is the common case.
Check every domain is actually registered in both. One of mine was missing from Bing entirely and I had never noticed.
After submitting, wait and check the status reads Success with a page count, not just "submitted". Mine sat on "Couldn't fetch" for a few minutes before flipping.

None of this is clever. It is the boring last step that the tutorials imply happens by itself.

I build a set of small SaaS tools, one of which is a visibility auditor, which is how I noticed. It scored several of these sites highly while their sitemaps had never been submitted, because it only fetched the URL it was given. I have since fixed that too.