What is AMP?

AMP (Accelerated Mobile Pages) is a format for publishing web pages with restricted HTML, a JavaScript runtime and custom components. The project’s specification describes performance as a design goal and permits ordinary web-server delivery as well as optional proxy serving.

The AMP HTML specification describes a runtime that implements components and manages resource loading. Components provide features such as image galleries; the format also has rules for markup, styles and layout.

A framework label should not replace a feature review. Identify which pages use it, what a visitor needs to do and how the actual output is delivered before deciding whether to retain or change the implementation.

Separate document format from delivery

The specification says a document can be served like ordinary HTML from a web server or optionally through a specialized proxy. The project’s cache overview describes a cache as a proxy-based content delivery network and says the linking platform chooses which cache, if any, to use.

Record the origin document and the path visitors actually use. Do not infer that every request comes from Google’s cache or that every browser displays a Google-hosted URL. The format, stored copy and navigation experience are different parts of an implementation.

How do AMP canonical links work?

A paired deployment has a non-AMP canonical page that points to its alternate with rel="amphtml", while the alternate points back with rel="canonical". The specification also permits standalone canonical AMP: that document points to itself and needs no amphtml relation to another page.

These example URLs show the head annotations for a paired deployment.

<!-- In https://example.com/guide.html -->
<link rel="amphtml" href="https://example.com/guide.amp.html">

<!-- In https://example.com/guide.amp.html -->
<link rel="canonical" href="https://example.com/guide.html">

The canonical relationship describes which version represents the content; it does not say that a cache must serve every request. See Canonical URL for the broader distinction between a declared preference, Google’s selection and a redirect.

Compare the deployment you actually maintain

Use this planning aid to compare the documents, visitor tasks and maintenance work in each setup.

Deployment choices and inspection work
SetupWhat to inspectWork to account for
Paired versionsBoth documents, their annotations and the visitor’s taskKeep corresponding content and actions consistent
Standalone canonical pageThe document’s own canonical and supported featuresMaintain the format without assuming a separate ordinary-HTML twin
Proposed replacementThe new page, old addresses and linking referencesPlan the transition and verify functionality rather than assuming a framework switch fixes performance

Google’s current AMP guidance says pages can be viewed on all device types and should use responsive design. It allows considering a standalone setup when the format supports the functionality required. Responsive design and this technology are therefore not mutually exclusive alternatives.

A fictional publisher’s feature review

Imagine a fictional publisher maintaining paired versions of a guide. An editor updates the ordinary page with a correction and a new filter, while the alternate still shows the old text and lacks that interaction.

The review checks the published text, supported filter behavior and annotations on both versions. The team can then compare the work needed to keep the pair consistent with the work needed for a replacement.

Google’s current guidance says Search indexes these pages like other web pages and applies the same standard regardless of the technology used. For paired pages, users should be able to experience the same content and complete the same actions as on the corresponding canonical page, where possible.

Google’s April 2021 page-experience announcement said the AMP format would no longer be required for the Top Stories carousel.

Keep validation, measured loading and responsiveness, accessible interaction and search outcomes separate. A valid document does not supply an observed Core Web Vitals result or prove that a reader completed a task. Those checks need their own evidence.

Check functionality and update responsibility

Custom JavaScript is not categorically impossible. The amp-script component documentation describes custom code running in a Web Worker with a virtual DOM. Its restrictions cover matters including code size, user-triggered changes and script hashes. This is constrained component behavior, not unrestricted browser scripting.

List the components, required interactions and integrations your pages use. Check their current documentation and validation output before changing the template. Assign who updates the source content, alternate output and any dependent integrations; keep failures visible rather than assuming the framework handles every requirement.

For each change, retain the relevant URLs, source version, validation result and task checks. Measure representative visits or controlled tests under stated conditions when performance is the question.

Do not diagnose the format from an absent link

The specification requires an AMP document marker, runtime and canonical annotation, and allows a self-referencing canonical when no ordinary-HTML version exists. Absence of a separate amphtml link therefore does not rule out a standalone implementation.

Inspect the returned document rather than relying on an /amp/ filename or the absence of a dashboard report. If removal is proposed, first identify whether the page is an alternate or the only canonical version and what should remain available. A generic instruction to delete every such URL can lose the intended page.

Retaining an existing setup and replacing it both require maintenance decisions. Compare supported features, editorial consistency and observed experience. Do not prescribe one choice for every new site or make a passing metric a universal prerequisite for every change.

Use Page Speed for the broader performance concept and Core Web Vitals for specific experience measurements. AMP is a document technology; neither a component name nor a cached copy establishes those measurements.

Sources and scope

The technical distinctions use the AMP Project’s HTML specification, cache overview and the relevant amp-script usage and restrictions. Google’s current Search guidance supplies its page standards; the 2021 announcement is cited only for the historical requirement change. The paired URLs and publisher scenario are illustrative. No AMP document, cache path, account or performance outcome was tested for this entry.

Explore this topic: AMP and SEO in 2026: Is It Still Worth Implementing?.