What you're buying when an agency says "modern stack"

One. How are pages delivered? Pre-rendered and served as files, or built per request? This is the one with a measurable consequence: it sets the performance floor against Web Vitals, and it decides whether your content exists without JavaScript executing.

Two. Who can edit a page? You, in an editor, or a developer, in a repository. In our experience this is the decision made by the agency and regretted by the client.

Three. Who patches it? Every dependency ages into disclosed vulnerabilities — OWASP carries Vulnerable and Outdated Components as a category of its own. Somebody owns this monthly or nobody does.

Four. Can you leave with it? Source, database, and a signed assignment.

No documented ranking system takes the stack as an input. Google's SEO starter guide applies identically to every one of them. Nothing in the documentation stops a well-configured older stack from outranking a badly configured new one.

So modern stack is a claim about questions one and three, and those have checkable answers. Two worth asking out loud: does my content render without JavaScript — turn it off and look — and who applies dependency updates, how often, and what do I receive as evidence? A changelog with versions and dates, or nothing.

What to be wary of: a rebuild justified by the stack alone. If the fix list is content, indexation and copy, a new framework changes the invoice and not the outcome.