Bad SEO or Good SEO with Webstudio/Airtable?

At a glance

The post discusses the impact of using a REST API backend (like Airtable) with WebStudio on SEO. Community members share their experiences and recommendations:

- Dynamic content is server-side rendered, and search engines are indexing pages correctly. However, Airtable's slow response times can affect load speed.

- Baserow is recommended as an alternative to Airtable, but there are limitations on chaining multiple bases to handle large-scale content (1 million+ pages).

- Cloudflare caching can help optimize speed, but has limitations. A custom backend solution using a worker wrapper is suggested to handle large-scale content.

- Community members use templates for sitemaps and configure meta tags in page settings to handle API-driven pages.

- Baserow has a limit of 10 simultaneous API connections, which may not be practical at scale, but is fine for most use cases.

DDerrick

Hey WebStudio Creators!
For those using a REST API backend (like Airtable) with WebStudio, how has it impacted your SEO? I’m curious about a few things:

Are search engines indexing your pages correctly, especially dynamic content?
Any issues with client-side rendering delaying how content appears to bots?
How do you handle meta tags, structured data, or sitemaps for API-driven pages?
Have you faced challenges with API performance or Airtable’s response times affecting load speed?

Would love to hear your experiences, solutions, or best practices! SEO is a big focus, and any insights would be super helpful. 🚀

12 comments

BBogdan

Dynamic content is server side rendered, nothing is delayed

Airtable is just slow. We recommend using Baserow as alternative.

DDerrick

Hey @Bogdan thanks for getting back. Interesting, can pages be cached with cloudflare workers to optimize speed?

Would you reccomend baserow for 250k pages (max rows)

Also isit possibe to chain (connect) mutiple bases as im aiming for 1 mill + pages...

BBogdan

Cloudflare does caching for small time but not heavily, we will improve this soon.

Resources cannot be chained, so you need custom backend for this, maybe via worker.

BBogdan

We have templates for sitemaps
and meta tags are configured in page settings

DDerrick

Ok so self hosting baserow is best bet @Bogdan ?

BBogdan

If you need. By custom backend I mean something like worker wrapper which would compose baserow calls and output data as single request

JJohn Siciliano

Are search engines indexing your pages correctly, especially dynamic content?

yes, it's a page like any other on your site in the eyes of viewers/search engines. Dynamic sitemaps even include all the variations of the dynamic page.

How do you handle meta tags, structured data, or sitemaps for API-driven pages?

Data bindings so you can make the title, social graph image, json ld, etc dynamic (we have videos on this)

DDerrick

Thanks @John Siciliano & @Bogdan

DDerrick

I'd love to send you a PM @John Siciliano - added you as a friend.

DDerrick

Baaserow limit of 10 api hits per srcond, is that impractical?

JJohn Siciliano

I'm on the fence about it. Most queries resolve in less than a half second. So 10 people would need to request basically at the same time. At scale, not practical, but for most use cases its fine

JJohn Siciliano

I dont think its per second btw, I recall it being 10 simulatenous connections

Add a reply

Join the Webstudio community

Bad SEO or Good SEO with Webstudio/Airtable?