AMP页面部署路径决策：合并主路由的优劣及谷歌观点咨询

Great question! Let’s break down the pros and cons of shifting your AMP page from the /restaurant/:id/amp sub-route to the main /restaurant/:id route—since your two pages are nearly identical in functionality, this is a totally reasonable consideration.

Pros #

• Simplified routing & reduced maintenance overhead
  Ditching the separate /amp route means you only have one set of code and one route to maintain. No more syncing updates, bug fixes, or content changes across two nearly identical pages—this cuts down on redundant work and lowers the risk of inconsistencies.
• Improved user experience
  Users won’t need to seek out or remember the /amp sub-route to get the fast-loading AMP experience. Anyone visiting the main restaurant page (whether via search, links, or direct navigation) will immediately benefit from AMP’s speed, especially mobile users who make up a large portion of search traffic.
• Eliminates duplicate content risks
  Even if your two pages are identical now, over time small differences could creep in (e.g., updated content on one route but not the other). Serving AMP directly on the main route removes the chance of search engines flagging duplicate content, which can harm your SEO rankings.
• Unified analytics & tracking
  You’ll no longer need to split traffic analysis between two routes. All user interactions, page views, and conversion data will live in one place, making it easier to get a clear picture of how your restaurant pages perform.

Cons #

• Limits future feature flexibility
  AMP has strict rules around allowed HTML, CSS, and JavaScript. If you ever want to add non-AMP-compatible features to your main restaurant page (like complex custom interactions, third-party widgets, or dynamic content that AMP doesn’t support), you’ll be stuck—you’d either have to rebuild the page outside AMP or create a new sub-route again.
• Requires handling existing /amp route traffic
  If your /amp route has already been shared by users, linked from other sites, or indexed by search engines, shutting it down without proper redirects will result in 404 errors. You’ll need to set up 301 redirects from /restaurant/:id/amp to /restaurant/:id to preserve user experience and SEO value, which adds a small but necessary setup step.
• Potential desktop experience tradeoffs
  AMP is optimized for mobile performance, but it can feel restrictive on desktop. If your desktop users expect richer interactions or a more robust layout that AMP’s constraints don’t support, serving AMP on the main route might lead to a less satisfying desktop experience. You could mitigate this with responsive AMP, but it still won’t match the flexibility of a non-AMP desktop page.
• AMP cache reconfiguration
  If you’ve been using Google’s AMP Cache for your /amp route, switching to the main route will require updating your cache configuration. You’ll need to ensure the cache indexes and serves the main route’s AMP content correctly, which may involve revalidating your site or adjusting AMP-specific meta tags.

Quick Recommendation #

If you’re confident that your restaurant pages won’t need non-AMP features in the foreseeable future, this switch is a great move—it simplifies your stack and improves user experience. If you’re unsure, consider starting with a 301 redirect from /amp to the main route and monitoring traffic, user engagement, and SEO metrics for a few weeks before fully retiring the sub-route.

内容的提问来源于stack exchange，提问作者Adam Young