FOR EXISTING SITES
Don't want to rebuild, but want to be cited by AI search? TrendPackage's source provision service brings your existing site up to TP-quality AIO with minimal code changes. This page maps technical compatibility by construction pattern.
QUICK ANSWER
Q. In one line: which sites are supported?
A. Sites where HTML can be injected into the head/footer, or where template files are directly editable. This includes Next.js, WordPress (custom theme or HTML-injection plugins), Shopify (Liquid edit access), SSG like Astro, and static HTML. Pure no-code platforms (Wix, STUDIO, etc.) are not supported.
COMPATIBILITY TIERS
Three axes: (1) Can HTML be injected? (2) Can article pages be added? (3) What's the Stem integration method? These determine the tier, implementation difficulty, and delivery time.
TP's source code is mostly drop-in. Full structured data (7 schemas) + verification (5 engines) + IndexNow.
STACKS
Next.js / Nuxt / SvelteKit / Remix
Edit layout directly, server-side fetch with ISR 60s
Astro
Embed schemas in Layout.astro, build-time + ISR
HTML injection works fine. Column integration depends on platform (WP post / build webhook).
STACKS
WordPress (custom theme / functions.php access)
meta + JSON-LD via wp_head hook, Stem → WP posts via REST API
Shopify (theme.liquid edit access)
Embed schemas in theme.liquid, Shopify Blog API + Stem webhook
Static site generators (Hugo / Jekyll / 11ty)
Edit layout template directly, build-time fetch + auto-deploy webhook
Vue / React SPA (SSR-required)
Equivalent to Tier 1 once SSR-ified. CSR alone may not let AI bots read JSON-LD.
HTML injection works but column delivery is weak. Manual updates or partial SSG-ification.
STACKS
WordPress (plugins only, no theme edit)
Use Insert Headers and Footers etc. for wp_head injection. WP REST API posting requires additional permissions.
Static HTML (manual edit)
Direct edit works for meta/schema. Columns require manual HTML adds or SSG migration.
CSR-only SPA (SSR not viable)
AI bots may not pick up structured data. Strongly recommend SSR / prerender.
NOT SUPPORTED
In these cases, the realistic options are "migration to Next.js / WordPress custom theme (replacement)" or declining. We will be straightforward about this during diagnosis.
COLUMN INTEGRATION
For any compatible site, we strongly recommend continuous column generation. AI citation works best when structured-data-rich long-tail content accumulates monthly. Stem fully automates generation, JSON-LD attachment, and delivery — zero ops burden on the customer.
STEM INTEGRATION PATTERNS
Stem cron @ 09:00 JST daily → Gemini generates articles + auto JSON-LD → Stem DB → site fetches via getColumns() API → ISR 60s renders /column/[slug]. FAQPage / HowTo / Article schema picked up by AI Overview.
Stem POSTs to client WP site /wp-json/wp/v2/posts (Application Password auth) → WP holds as standard post → custom theme renders FAQ schema as JSON-LD.
Stem cron → generates articles + DB save → triggers GitHub / Vercel webhook → build fetches from Stem API → articles converted to MD for SSG → deploy.
Stem admin generates articles → owner manually pastes HTML into site → JSON-LD schema via pre-provided snippets. Some manual lift but functional.
How to choose: We select the optimal pattern automatically during the tech stack diagnosis. Customer makes no decision. Included in the monthly Stem ongoing operations option (¥30,000/month).
GET STARTED
From ¥360,000 one-time (scale-dependent) / 3-4 week delivery
Free initial diagnosis to assess tech stack, then formal quote. We disclose non-support cases upfront, before any contract.
Compatibility varies by construction method. We will be honest during diagnosis.