$ SSH · codebase discovery · surgical file writes
Custom PHP SEO automation
Coming Soon
Autonomous SEO for Custom PHP Sites
Every competitor says 'sorry, we don't support custom CMS.' effectly.ai says 'give us the credentials.' Via a scoped SSH keypair, effectly.ai reads your custom PHP application — whatever the structure — and writes meta tags, schema markup, sitemap files, and redirect rules directly to your code. Legacy app, custom framework, hand-rolled CMS — if it runs PHP and you can SSH in, effectly.ai can fix its SEO.
custom PHP SEO automation · legacy CMS SEO · PHP SEO tool · custom CMS SEO automation · SSH SEO automation PHP
The moat
Most SEO automation stops where the vendor's integration list stops. effectly.ai stops at the edge of your server: scoped SSH, real files, real rollback. No "migrate to WordPress first." No "enterprise sales call." If your stack is PHP and you can authorize a key, we can meet your templates where they live.
How it works
01
Scoped SSH key
Same security model as WordPress VPS and Laravel: a dedicated keypair, `command=` restriction, path-limited access to your web root — no interactive shell, no lateral movement outside the project.
02
Codebase discovery
effectly.ai maps your directory layout, finds template and include patterns, and locates where HTML is assembled — without requiring Laravel, Symfony, or any named framework. Output points for `<head>`, headers, and footers are inferred from structure and conventions.
03
Surgical writes
Meta blocks, JSON-LD script tags, `sitemap.xml`, `robots.txt`, and `.htaccess` redirects are written to the files that actually serve your site — not a parallel system that drifts from production.
What effectly.ai writes
| Element | Example |
|---|---|
| PHP templates | `<head>` meta tags, title/description in layout files |
| Schema JSON-LD | `<script type="application/ld+json">` blocks where your HTML is built |
| sitemap.xml | Static file or generator entry point your server already exposes |
| .htaccess | Redirect rules, basic cache and security headers where appropriate |
| robots.txt | Crawl directives and sitemap references |
| HTML templates | `<title>`, `<meta>` in any template or partial your app includes |
| Content templates | Internal link `href` updates in body templates when part of an SEO fix |
What other SEO tools say vs. effectly.ai
What other SEO tools say
- "We don't support custom CMS"
- "Please migrate to WordPress first"
- "Our plugin requires [specific framework]"
- "Contact our enterprise team" (translation: we can't help)
effectly.ai
- Give us SSH credentials. We'll figure out the rest.
- No framework requirement — PHP is PHP.
- Template structure auto-detected.
- Same rollback, same safety, same Constitution Agent.
Get notified when Custom PHP integration launches
One email when this integration is live in the dashboard. No spam.
Technical details
Auth & scope
Scoped SSH with wrapper-only execution and path restriction to your deploy root. Secrets and credentials outside the allowed tree are never targeted for writes.
What we read
PHP, HTML, and config files under the allowed path; optional read-only hints from environment for base URL — without writing `.env`.
What we write
Templates, partials, sitemap and robots files, and server config snippets you already use — always as normal file changes you can diff and revert.
Safety
No automatic mass refactors. Changes are scoped to SEO outcomes; snapshots and git history follow your org's SSH integration policy.
FAQ
Will this break my 10-year-old app?
Changes are small, file-local, and reviewable — meta and schema in known templates, sitemap and robots as explicit files. You keep your deploy process; we do not replace your runtime. If a change is risky for a legacy pattern, effectly.ai can flag it for human approval first.
What if our PHP layout is non-standard?
Non-standard is normal here. Discovery is structure-driven: where HTML is built, where includes chain, where a global header lives. effectly.ai does not need your app to match a framework diagram — only to expose editable files over SSH.
Is SSH safe on older infrastructure?
The key is scoped: no full shell, no sudo, path-limited. You rotate or revoke the key anytime. effectly.ai never stores your server password — only the same key-based access model as our other SSH integrations, with audit trails per change batch.
Do we have to migrate to a modern CMS?
No. That is the point of this integration. Migration is a business decision, not a prerequisite for better SEO execution.