Softr's real SEO happens in your data, not your settings

Most of what decides whether a Softr site is found is configured per item, in fields that come from your data source, and that are empty until you add them.

Claims on this page were last checked against the platform's own documentation on .

See what a crawler gets

Softr creates a sitemap automatically at yourdomain.com/sitemap.xml. Item detail pages carry their own SEO fields, driven from your data: SEO:Index to decide whether the item is indexed and added to the sitemap, plus SEO:Title, SEO:Description and SEO:Slug. Item pages are not individually indexable until those fields exist and SEO:Index is positive.

What Softr does for you

The sitemap is automatic. Softr creates it and serves it at yourdomain.com/sitemap.xml, so there is nothing to write or generate yourself.

Softr's documentation notes that for sites with a large number of entries, more than a thousand, you can visit your site URL with /generate-sitemap appended to regenerate it. Worth knowing if your sitemap looks stale or incomplete on a large catalogue.

General SEO settings live in the app's settings, and per-page SEO details are set in page settings. There is a robots.txt you can fill in with instructions for crawlers, and custom domains are supported.

So the site-level basics are handled. What is not handled by default is the part that matters most on a Softr site, which is the item pages.

The four fields that decide everything

This is what makes Softr different from the other platforms in this section, and it is the reason this page exists.

A typical Softr site is built on a data source, and its most valuable pages are item detail pages: one page per record. Those are the pages that answer specific questions and can be found individually, and they are the whole point of building on a list.

Softr's documentation describes setting up SEO parameters on your item details data in order to index each item as a separate page discoverable by search engines, with a custom slug and metadata. The fields are SEO:Index, which indicates whether the item page should be indexed and accepts yes/no, 1/0 or true/false values, SEO:Title, SEO:Description, and SEO:Slug.

The documentation states that if SEO:Index is positive, the page will be indexed by search engines and added to the sitemap. Which tells you what happens when the field is absent or negative, and that is the state most Softr sites are in without anybody realising.

Why this catches people

The site works perfectly. You browse the list, click through to an item, and the detail page renders with the right content. Nothing suggests a problem.

But the indexability of that page is a property of the record behind it rather than of the page you are looking at, and it is controlled by a column that may not exist in your data source at all.

So the failure is invisible in the way that matters most: everything a human does works, and the thing a crawler needs was never created. This is the same shape as the Bubble privacy-rule problem and the Framer per-page toggle, and it is why per-item configuration deserves its own check.

The practical version: open your sitemap and count. If your catalogue has four hundred items and the sitemap has eleven URLs, the fields are missing.

Writing the fields properly

Since these come from your data, they can be generated rather than typed, and that is worth setting up once.

SEO:Title should read as an answer rather than as the record name. A field containing only the item's name repeats what the heading already says and spends the most valuable position on a word that may match nothing anybody searched. Build it from the record: the name plus what it is for, in the words a person would use.

SEO:Description should be specific to that record rather than a template with one variable swapped. A description that is identical across four hundred items except for a name is close to one description repeated four hundred times.

SEO:Slug wants to be short, readable and stable. Changing a slug later changes the URL, which means anything that had been indexed at the old address has to be redirected.

And SEO:Index gives you a genuine editorial control worth using. Thin records, duplicates, and placeholder entries are better left out than indexed, because a set of weak pages drags on the whole site.

The site around the items

Item pages answer one narrow question each, which is valuable and is not the whole job.

The pages that bring people in are usually a level above: the guide that explains the category, the comparison, the how-to that somebody searches before they know your listing exists. Those are ordinary pages you write, and Softr's page-level SEO settings apply to them normally.

The strongest structure is the same one that works everywhere: a set of guide pages answering real questions, each linking down into the relevant item pages, and the item pages linking back up. That gives a crawler a reason to reach the items and gives a reader a reason to move between them.

A Softr site with four hundred well-configured item pages and no guides above them is a catalogue nobody has a route into.

The check to run today

Three things, in order, and the first takes ten seconds.

  • Open yourdomain.com/sitemap.xml and count the URLs. Compare that against how many items you expect to be findable.
  • If the count is low, look at your data source for the SEO:Index column. If it does not exist, that is the answer.
  • Check that SEO:Title and SEO:Description exist and vary genuinely between records rather than being one template with a name swapped in.
  • Confirm you are on a custom domain, and read your robots.txt to make sure nothing you want found is excluded.
  • Then verify in Search Console and submit the sitemap, since Softr generating one does not tell Google it exists.

Part of a larger guide

This page is one part of Vibe coding SEO. The other parts:

Questions people ask

Does Softr create a sitemap automatically?
Yes, and it serves it at yourdomain.com/sitemap.xml with nothing to write yourself. For sites with more than a thousand entries, Softr's documentation describes appending /generate-sitemap to your site URL to regenerate it.
Why are my Softr item pages not indexed?
Almost always because the SEO fields on your item details data are missing. Softr's documentation describes SEO:Index as indicating whether the item page should be indexed, and states that if it is positive the page is indexed and added to the sitemap. Absent or negative, it is not.
What are the Softr SEO fields?
SEO:Index, which accepts yes/no, 1/0 or true/false and decides indexing and sitemap inclusion, plus SEO:Title, SEO:Description and SEO:Slug for the metadata and the URL of each item page. They come from your data source rather than from page settings.
How do I check whether my item pages are set up?
Open your sitemap and count the URLs, then compare that against how many items you expect to be findable. A catalogue of four hundred items with eleven URLs in the sitemap tells you the fields are missing.
What should SEO:Title contain?
An answer rather than the record name. A title containing only the name repeats the heading and spends the best position on a word that may match nothing anybody searched. Build it from the record: the name plus what it is for, in the words a person would use.
Are item pages enough on their own?
No. They answer one narrow question each and give a reader no route in. The pages that bring people are a level above: guides and comparisons that somebody searches before they know your listing exists, each linking down into the relevant items.

Count what is actually in your sitemap

The free crawler view fetches your sitemap and robots.txt and reports what they contain, which is the fastest way to spot missing SEO fields.

See what a crawler gets Have Licheo do it for you