Editorial Standards

Submission Guidelines

The editorial rules every Make An App Like contributor follows. Read this once, ship faster on every submission, and skip the back-and-forth with our editors.

The quality bar

Every submission must clear these five

We reject roughly 30% of submissions on a first read — almost always because the draft missed one of these five. Save a credit and self-check before you click submit.

Original, never-before-published

No syndicated copy, no AI-spun rewrites of existing articles. We check every submission against Copyscape + an AI-detector before review.

1,500+ words for category guides

Long-form ranks. We expect at least 1,500 words for category-vertical pieces; comparison and teardown articles typically land between 2,200–3,200 words.

Concrete and decision-grade

Every claim cites a number, a source, or a real example. No hedging adjectives, no "many experts agree", no rounded-up traffic stats.

At least two authoritative sources

Link to primary sources (vendor docs, research papers, government data) — not Medium hot-takes or other guest-post sites. We strip low-trust outbound links during review.

Plagiarism + AI-detection clean

Submissions failing Copyscape or AI-detection above 35% are rejected automatically. Use AI as a research assistant, not a ghost-writer.

Voice + formatting

Write like a senior practitioner

Make An App Like readers are founders, engineers, and product managers. They have seen every generic listicle. The articles that win — both on Google and as ChatGPT/Perplexity citations — sound like a person who has actually shipped the thing they are writing about.

Do this

  • Open with a 2–3 sentence hook that answers searcher intent immediately.
  • Sound like a senior practitioner — confident, plain-spoken, sceptical of hype.
  • Cite concrete numbers, pricing, or latency figures when relevant ("$0.003 per request, 1.2 s p50 latency").
  • Use semantic HTML: <h2 id="…">, <h3 id="…">, <p>, <ul>, <ol>, <table>, <blockquote>, <code>.
  • Add an id attribute (kebab-case) to every heading so it deep-links cleanly.
  • Tables for comparisons. Code blocks for code. Never paste a screenshot of text you could just paste as text.

Cut these phrases

Auto-flagged in review. Every one of these signals a generic blog template and weakens the article.

  • "In conclusion"
  • "Welcome to our blog"
  • "Without further ado"
  • "It is important to note that"
  • "In today's fast-paced world"
  • "Revolutionary", "groundbreaking", "magical", "just works"
  • "AGI", "human-level"
  • "As an AI assistant" or similar self-references
Technical formatting

Markup, media, and links

HTML structure

Semantic tags only — <h2>, <h3>, <p>, <ul>, <table>, <blockquote>. Never <h1> — the site renders the title from the row.

Images + media

WebP or PNG, max 800 KB. Descriptive alt text on every image. No stock photos of people pointing at laptops. Charts, diagrams, and product screenshots only.

Outbound links

External links use rel="nofollow noopener". Link to primary sources (vendor docs, research papers, official datasets) — not other guest-post sites or low-trust aggregators.

Submission process

From draft to live in five steps

  1. 1

    Read this page

    Confirm your topic fits one of our active categories and that your draft meets the quality bar below. Submissions that ignore the guidelines get rejected faster than the editorial review queue.
  2. 2

    Sign up + activate

    Create a contributor account at /write-for-us-technology. Public providers like Gmail and Outlook are blocked — we onboard via business email so we can verify your brand.
  3. 3

    Draft in our editor

    Rich-text editor with SEO fields (meta title, description, focus keyword), Claude-powered AI assist, image uploads, and live preview. Drafts auto-save every 30 seconds.
  4. 4

    Submit for review

    One credit per submission. Editors either approve, send back inline feedback, or reject with clear reasons. Median turnaround is under 30 minutes during US business hours.
  5. 5

    Live with full SEO

    Approved articles ship with schema markup, OG cards, AI-generated thumbnails, internal-link injection, and same-day indexing via IndexNow + Google Indexing API.
Clone Apps listings

Stricter rules for buyable services

Clone Apps live at /white-label/<slug> and are buyable services, not editorial blog posts. The public page is part of our catalogue — consistency across listings matters more here than anywhere else on the site.

Industry is required

Every clone is tagged with a primary Industry (Real Estate, Automotive, Healthcare, Dating, etc.). The breadcrumb on the public page renders Home › Clone Apps › Industry › Clone name, and the vertical landing page at /buy-white-label-<industry> uses this tag to list your clone.

Rating is always 5.0 / 5

Every published clone is a vetted, deployment-grade product with the same buyer-satisfaction promise. The public page renders 5.0 uniformly. Prose in the body, FAQs, and meta description must match — never quote 4.7, 4.8, 4.9 anywhere.

Buyer voice, not reader voice

Write to founders evaluating a white-label deployment, not casual readers. Concrete, decision-grade language. No "in conclusion", no "let's dive in", no fluff transitions.

Pricing + timeline alignment

Mirror site defaults: $4,500–$18,000 one-time, 14–21 day delivery, 6 months free support, 7-day money-back guarantee. Don't invent custom numbers.

CTA wrapping

Every inline call-to-action goes inside <p class="cta-lead"> so the lead modal can hook the click. Lead copy: "Request a free demo".
Off-limits

What we don't publish

Submitting any of the below burns a credit and gets the article rejected on sight. If a topic is borderline, ask an editor before drafting.

  • Casino, sportsbook, or gambling promotional content (even if framed as "tech").
  • Adult or NSFW material in any category.
  • Cryptocurrency price predictions, "investment advice", or token shilling.
  • Spun, rewritten, or syndicated content from other publishers.
  • Generic "10 tips" listicles with no original framing or data.
  • Sponsored placements masquerading as editorial. We label paid content clearly.
  • Content that violates a vendor's trademark or terms of service.
After publication

Once an article is live

Slug is locked

The article URL becomes part of our canonical SEO record. To rename, contact an editor — we will set up a 301 redirect from the old slug rather than just changing the live URL.

Edits re-enter review

Editing a live article kicks the change back into the editorial queue. The new version ships once an editor approves it; the original article stays public in the meantime — no broken-link windows.

SEO maintenance

We re-index every article periodically and update schema markup as Google's spec evolves. Article rankings stay live for the lifetime of the domain — no surprise takedowns or year-one expirations.

Read this page first

Ready to ship a piece that actually ranks?

Articles that follow these guidelines clear review in under 30 minutes and ship live the same day. Skim them once, draft against the checklist, and you will not see a rejection email.