Hire Accelerated Mobile Pages (AMP) Developers

AMP (Accelerated Mobile Pages) is an open-source HTML framework originally developed by Google to create fast-loading pages for mobile users. AMP pages use a restricted subset of HTML, AMP-specific JavaScript components, and a caching layer (the Google AMP Cache) to deliver pages extremely quickly on mobile connections.

The official AMP plugin for WordPress (developed by the AMP team and XWP) handles the conversion of WordPress pages to AMP-compliant format. It operates in several modes: Standard (the entire site uses AMP), Transitional (both AMP and non-AMP versions exist), and Reader (separate AMP templates for content pages). Each mode has different implications for how the site is built and how much of the existing theme and plugin functionality carries over.

AMP’s role has evolved since its introduction in 2015. Google removed the requirement for AMP in the Top Stories carousel in 2021, reducing one of the main SEO incentives for AMP adoption. Core Web Vitals can now be achieved without AMP. Many publishers are evaluating whether AMP is still worth the maintenance overhead for their specific situation. For sites already running AMP, developer help is often needed to fix validation errors or maintain AMP compatibility as the site evolves. How To Fix Core Web Vitals WordPress.

AMP development work on WordPress typically involves:

• Initial AMP plugin setup and configuration – choosing the correct mode, resolving AMP validation errors, and ensuring the AMP version of the site is functional.
• Fixing AMP validation errors – invalid markup, unsupported scripts, or AMP-incompatible CSS that the AMP validator flags as errors.
• Making custom themes AMP-compatible – converting non-AMP theme templates to AMP-compliant HTML, replacing standard JavaScript with AMP components.
• AMP-compatible forms and interactive components – replacing standard form handling with AMP form component, implementing analytics with AMP analytics.
• AMP and analytics setup – configuring AMP analytics to track page views and events in Google Analytics or other analytics platforms from AMP pages.
• Evaluating whether to remove AMP – auditing the site’s AMP implementation and Core Web Vitals to determine if AMP removal is advisable.

AMP development is a specific skill – the AMP HTML specification, AMP components, and the WordPress AMP plugin’s validation system are all unique. Look for developers who have specifically worked with AMP on WordPress rather than general front-end developers who have not.

Ask whether they have experience with the AMP validator and the specific types of validation errors that AMP sites encounter. Common errors – inline styles exceeding limits, invalid HTML elements, unsupported JavaScript – each have specific AMP-compliant solutions that require AMP knowledge.

For new AMP implementations, ask their honest opinion on whether AMP is appropriate for the specific site. A developer who raises the question of whether AMP is still the right choice – given that Core Web Vitals can be achieved without AMP – is thinking about the client’s interests rather than just completing the task.

Common AMP + WordPress problems: How To Fix Core Web Vitals WordPress.

• AMP validation errors on published pages – a theme or plugin is outputting markup or JavaScript that AMP does not allow. Use the AMP plugin’s validation report to identify the source and apply the AMP-compatible alternative.
• AMP pages missing content visible on the non-AMP version – a plugin that adds content via JavaScript is not AMP-compatible and its output is stripped on AMP pages. Find the AMP component equivalent or disable the plugin on AMP pages.
• Analytics not firing on AMP pages – AMP uses its own analytics system (amp-analytics component) rather than standard JavaScript analytics. Standard Google Analytics code does not run on AMP pages. Configure amp-analytics to track events instead.
• AMP version looking different from the non-AMP version – the AMP plugin’s CSS sanitisation is stripping CSS that the AMP page depends on, or the AMP mode is using a different template. Review the AMP plugin’s CSS tree-shaking settings and template configuration.

AMP pages need to be validated whenever the site changes – theme updates, plugin updates, or new content types can introduce new AMP validation errors. Running the AMP validator regularly catches errors before they affect Google’s crawling of the AMP versions.

The AMP plugin for WordPress updates regularly. Major updates sometimes change which CSS is kept and which is removed (tree-shaking), which can affect AMP page appearance. Testing AMP pages after major AMP plugin updates is important.

The AMP space continues to evolve. Monitoring whether AMP is still serving its intended purpose – improved mobile performance and user experience – through Core Web Vitals data for AMP vs non-AMP pages informs the decision of whether to maintain the AMP implementation long-term.

When posting an AMP project on Codeable, describe the current AMP setup – which mode the plugin is in, what validation errors appear, and what the AMP pages should look like versus what they currently look like. If the project is evaluating whether to adopt or remove AMP, describe the site’s traffic profile and Core Web Vitals scores so the developer can give an informed recommendation.