DOCSEARCHbyAlgolia
Submit Docs

Ampify Documentation

website·Indexed 33 days ago

https://duda-docs.ampify.io/docs/About_AMP/

Documentation for Ampify, a tool for creating AMP (Accelerated Mobile Pages) versions of sites. Includes guides on editor widgets, built-in analytics, URL redirects, HTML and CSS customization, and resolving Search Console errors.

Tokens
6.2K
Snippets
3
Records
59
Agent score
53%

What's inside Ampify

  1. Understand how AMP and Ampify improve site performance

    Accelerated Mobile Pages (AMP) is a web standard designed to make pages load near-instantly on mobile devices by pre-loading content. Using AMP typically results in higher Core Web Vitals scores, an average of 30% more search traffic due to improved SEO, and a significant reduction in bounce rates (up to 70% less loss compared to standard HTML pages). Ampify automates the creation and deployment of these AMP versions for sites that may not have the resources to build them manually.

  2. Understand the impact of Search Console errors on AMP pages

    When an AMP page triggers a Search Console error, Google automatically falls back to displaying the source HTML page. This fallback occurs without repercussions to the page appearance or search ranking. Once the underlying issue is resolved, the AMP version will be restored as the primary display version.

  3. Exclude popups from AMP pages to reduce CSS load

    Excluding popups allows them to open as new pages instead of overlays, which can help an AMP page pass validation without changing the overall page structure. There are three ways to implement this:
    <!-- Option 1: Exclude ALL popups site-wide -->
<script type="text/javascript">
  window.popup_amp_exclude = ["exclude_all_popups"]
</script>

<!-- Option 2: Exclude SPECIFIC popups site-wide -->
<!-- Replace names with the precise popup names from the Duda dashboard -->
<script type="text/javascript">
  window.popup_amp_exclude = ["popup_name#1", "popup_name#2"]
</script>

  4. How Google discovers and serves AMP pages

    Google serves AMP pages in mobile search results through the following process:

    1. An AMP version of a page is created to coexist with the standard HTML version.
    2. A special amphtml tag is placed in the HTML page's header to notify Google of the AMP version's existence.
    3. Google indexes the HTML page, discovers the amphtml tag, and validates that the AMP page meets all required restrictions.
    4. Once validated, Google optimizes the page, stores it in the AMP cache, and serves it in search results with the 'accelerated-page' badge.

  5. Use Custom HTML Widgets with Ampify

    Custom HTML widgets contain manually added code and are subject to the same AMP restrictions as manual site-wide customizations. Unlike other customizations, when a Custom HTML widget is present on a page, Ampify requires a specific review and approval of that widget before the AMP page can be published.

  6. Monitor AMP performance using Google Search Console

    To measure the actual impact of AMP on SEO and search rank, use the 'Core Web Vitals' tab in the Google Search Console. Google measures performance using real visitor data over several weeks. The goal is to achieve a 'good' score (indicated in green) for as many pages as possible to improve search rankings.

  7. Understand AMP URL redirects and SEO behavior

    AMP versions of pages use specific redirects to guide GoogleBot to the AMP content for indexing. Only AMP URLs have these redirects; standard HTML pages do not. For example, the AMP version of www.yoursite.com/ is www.yoursite.com/ampify/. These redirects are required by AMP and do not negatively affect SEO, nor do they redirect human visitors to a different domain.

  8. Disable reCAPTCHA for AMP page speed

    To improve AMP performance, disable reCAPTCHA validation using one of these two methods:

    1. In the form settings, uncheck the 'Add reCAPTCHA validation' button.
    2. If the button is unavailable, go to the settings menu, click 'Edit HTML/CSS', set the captcha value to false, click 'update', and republish the site.

  9. Handle HTML and CSS customizations in Ampify

    Ampify attempts to create an AMP version based on customized HTML or CSS edited via Developer Mode or a widget's 'Edit HTML/CSS' option. While it often digests these changes successfully, significant changes or those contradicting default AMP logic may cause discrepancies. Because Ampify cannot automatically detect if manual HTML/CSS changes were made, users must manually review the page design in the Ampify dashboard before approval, paying close attention to manually customized components.

  10. Hide elements from AMP pages to reduce CSS load

    Reducing the number of elements on a page reduces the CSS payload. You can hide elements in two ways:

    1. Hide from Mobile: Since AMP is based on the mobile version, setting an element to be hidden on mobile in the Duda editor will also hide it in the AMP version.
    2. Hide only from AMP: To hide an element specifically from the AMP version while keeping it visible on the standard mobile HTML page, add the amp_hide attribute to the element via the 'edit HTML' option.

  11. Request AMP support for custom built widgets

    Custom built widgets may require a dedicated setup to function correctly in their AMP version. Agencies with custom widgets should request support by providing a webpage containing the widget and the total number of websites where that widget is installed.

  12. Integrate third-party analytics providers for AMP

    To use non-Google analytics providers, you must use an AMP-specific tag provided by the vendor. These tags can be found via the provider's documentation or the AMP project site. Integrate these tags via Settings > Head HTML. The tag will only be active on the AMP version of the site and will be ignored by the HTML version.