Taskade Genesis

Get Your Published App Found in Search

Updated 2026-08-26·8 min read

Overview

A published Taskade Genesis app is a real website, so it can rank in Google and be summarized by AI assistants. The Branding panel is where you set what search results show, and the SEO Health checklist next to it scores your work while you type.

TL;DR: Open the Branding panel on a Taskade Genesis app and the SEO Health list scores your page title, description, site name, social image, search visibility, and measurement as you type. Verifying with Google is free on every plan. Every indexable app also serves robots.txt, sitemap.xml, and llms.txt automatically. See Publishing apps.

Open the SEO Health checklist

Open the app, click Publish in the top bar, then choose Branding. The app's Settings open on the Branding tab, and the SEO Health list sits beside the fields it grades.

Already in the full Settings window? Pick Branding from the list on the left. The long way round works too: Publish, then Advanced Settings, then All App Settings.

Each row carries one of three marks, and the mark is the score:

Mark Meaning
Green check Done. The value is valid, and Taskade uses it on your next publish.
Yellow alert Worth doing. Something is missing, or Taskade cannot accept the value.
Gray circle Optional, or a deliberate choice that is fine as it is.

The list grades the draft in front of you, not the live app. A green check means Taskade uses the value when you save and republish. A row your plan does not include shows a plan badge instead of a score.

Hide the app behind a site-wide password and two rows go gray on purpose: Google cannot reach the verification tag, and search engines never see the pages. Remove the password while you verify, then put it back.

Fill in what search results show

Editing these fields needs a Business plan or higher. On Free, Pro, or Starter you can still open the checklist, see where you stand, and verify the app with Google. The plan table further down spells out what each plan includes.

Work down the Basic Information and Social Media fields. These are the words a person reads before they decide to click.

  1. Page title. Aim for 50 to 60 characters. This is the blue line in a search result and the label on a browser tab.
  2. Description. Aim for 150 to 160 characters. This becomes the snippet under your link.
  3. Site name. Your company or brand name, used on social cards and search results.
  4. X (Twitter) handle. The account credited when someone shares your app on X. Optional, and safe to leave blank.
  5. Social image. Paste a full https:// web address. A relative path is not accepted, and Taskade falls back to a live screenshot of your app instead. Leave it blank on purpose and you get that screenshot, which is a fine default.
  6. Search visibility. For a public app, pick Allow indexing. For an internal tool, pick Don't index or Block completely. To have the page found but its links ignored, pick Index, no follow.

Choosing to stay hidden is a first-class option, not a mistake. The checklist marks it gray rather than nagging you.

Search engines are not the only route in. Publishing to the Taskade app showcase also puts the app in front of people browsing for something to clone.

Verify the app with Google Search Console

Verifying tells Google you own the site so you can see how it performs in search. This one is available on every plan, including Free, and it works on the address Taskade generated for the app. You do not need a custom domain first.

  1. Open Google Search Console and add your app's address as a property.
  2. Choose the HTML tag verification method.
  3. Copy only the content value from the tag Google shows you, not the whole tag.
  4. Paste it into Google Verification in the Branding panel and save.
  5. Republish the app, then click Verify in Search Console.

If the token is only partly pasted, the checklist reports that it does not look like a Search Console token. That is better than a green check that then fails at Google.

Measure visitors and set the app language

Two more fields sit under Verify and Measure, and both need a Business plan or higher.

  • Google Analytics. Paste your GA4 measurement ID, shaped like G-XXXXXXXXXX. Find it in Google Analytics under Admin, then Data Streams. Taskade adds the standard Analytics snippet on publish. If custom code already loads Analytics, Taskade skips the parts you already have so page views are not counted twice. The checklist shows which parts it adds.
  • Language. Pick the language your app is written in, so browsers and search engines label it correctly. The default is Auto (English).

You can always clear both fields, on any plan. Only a new value needs the plan.

Visitor numbers themselves live in a separate place. See App Analytics for the dashboard, which is also a Business feature.

Let crawlers and AI assistants find the app

You do not configure any of this. Publish an app that is set to be indexed and it serves three files on its own:

File What it does
robots.txt Welcomes crawlers, keeps them out of internal paths, and points at your sitemap.
sitemap.xml Lists your app's address so crawlers do not have to guess.
llms.txt A short plain-text summary for AI assistants: your title, your description, and a link to the app.

Each page tells search engines its own web address, so a deep page is listed as itself rather than as the home page. Taskade also adds a small block of site information (name, description, and image) in the format search engines read directly.

On the app's Taskade-generated address, a robots.txt, sitemap.xml, or llms.txt bundled with your app can replace the generated version. Custom domains differ: Taskade serves the platform robots.txt and sitemap.xml there, while a bundled llms.txt can still replace the generated file.

Choosing to stay out of search shuts these files down too, so hidden really means hidden:

  • Set the app to Don't index or Block completely and all three go dark. robots.txt becomes a blanket "do not crawl", and the other two stop answering.
  • Add a site-wide password and robots.txt becomes that blanket block as well, because a crawler cannot read the pages anyway.

Attach a custom domain and these discovery paths also answer on your own domain, with the override behavior described above.

Check which settings need a plan

Read this table before you promise a client a feature. It is the difference between two clicks and an upgrade.

Setting Plan
Google Search Console verification Every plan, including Free
Removing the Powered by Taskade badge Paid plans
Page title, description, site name, X handle, social image, search visibility Business and up
Google Analytics ID, app language, custom code in the head Business and up
App Analytics dashboard Business and up
Custom domain Business and up
robots.txt, sitemap.xml, llms.txt Every plan, automatic

If a workspace changes plan, you can still clear the Google Analytics ID, app language, and custom head code. You cannot edit or clear the page title, description, site name, X handle, and search-visibility fields on a plan that no longer includes them. Current plan details are on the pricing page.

Was this helpful?