SaaSAfterdark Growth audit
Menu

README.md About

About SaaSAfterdark, written like a README

SaaSAfterdark is a small SEO studio for lawful adult subscription platforms and the B2B tools that serve them. Like any good README, this page says what the project does, who it is for, what it will not do, and how to get started.

README.md

# SaaSAfterdark
Organic growth for adult platforms.

## Requires
- age verification where the law requires it
- verified uploaders and documented consent

## Does not support
- escort or commercial sex services

## What it does

We help adult platforms get found in search within the rules that govern them: state age verification laws, card network standards, and Google's policies on paywalls, SafeSearch and spam. The work covers marketing strategy, subscription platform SEO, technical SEO and membership growth. We specify and review; your developers build.

## Who it is for, and what it never does

supported Platforms we work with

  • Membership and subscription sites
  • Creator subscription platforms
  • Clip stores and marketplaces
  • Dating platforms
  • B2B tools for the industry: payments, verification, creator management, moderation

not supported What we never do

  • Help a platform bypass age verification, whether for visitors or search engines
  • Market content that suggests non-consensual activity or involves minors
  • Work with services that advertise escort or other commercial sex
  • Promise rankings, traffic or revenue
  • Name a client without written permission

Every platform we work with must verify the age and consent of people in its content. That is a card network requirement for adult merchants, and the minimum that protects real people.

## How we work

  • Specs, not slides. Findings arrive as tickets a developer can pick up, each with the reason it matters and how to check it is done.
  • Risk first. Anything that exposes member content or puts the merchant account at risk is fixed before any growth work begins.
  • Every release checked. Templates change, and a fix can be undone by the next deploy, so we look at staging and production after each release that touches public pages.
  • Dated claims. Anything we say about a law, a card network rule or a Google policy carries the date we checked it and the source.
  • Plain reports. Once a month: what moved, what we changed, what changed in the rules, and what comes next.

## Sources

Our research leans on primary documents first: Google Search Central's guidance on paywalled content, SafeSearch, crawling, spam and structured data; the published adult content standards of the card networks; the text of state age verification laws and the Free Speech Coalition's tracking of them; Ofcom's age assurance guidance for platforms with UK members; and federal and state rules on automatic renewal. Industry surveys and payment specialists' reporting appear too, always credited, with a note of what each one actually measured. Each note in our research shows when it was last reviewed.

## Known limitations

Every README should list what the project cannot do. Ours:

  • We are not lawyers. We summarize rules so pages and architecture can be planned; your counsel decides what applies.
  • We do not write production code. Your developers build; we specify and review.
  • We cannot control what AI assistants or review sites say about you, only make sure your own pages give them accurate material.
  • We have no published case studies yet, and will not have any until a client agrees in writing.

## First month

Once you have read the free audit and decided to continue, week one is access and a template map. Week two checks what crawlers receive on every template, logged in and out. Week three turns the findings into ranked tickets with your developers, starting with anything that exposes member content. Week four reviews the first fixes on staging and sets the keyword and tag policy. By day thirty you have the map, the tickets, the policy and a written note of what changed, and the next steps follow the 90-day roadmap.

## Getting started

  1. step 1
    Read the roadmap

    Our 90-day guide shows the order we work in.

  2. step 2
    Request a growth audit

    Free, confidential, and specific to your platform.

  3. step 3
    Choose a plan

    Prices are published on the pricing page.

The studio is young: no client logos or quotes appear on this site, and none ever will without the client's written approval.

Questions

Why only platforms that verify age and consent?

Because card networks require it of adult merchants, many laws do too, and it is the minimum that protects the people in the content. We will not help a platform grow that cannot show it.

Where is the team based?

We are a remote team. The legal entity that runs SaaSAfterdark appears in the terms of service and on each contract, and we work with platforms across several countries.

Can we see case studies?

Not yet: the studio is new, and a platform only appears in our marketing if it has agreed to that in writing. Judge us by the research on this site and by a free growth audit of your own platform.

Is there any obligation after the audit?

None. You receive a ranked, written list of risks and openings. If you want to continue, the first month turns it into tickets with your developers; if not, the list is yours to use.

next release Your growth audit

Find out what search can do for your platform.

  • Which public pages can rank, and which are hidden behind the age gate
  • Where members come from today, and where they could
  • No guesses about rankings, and no obligation
Request a subscription growth audit