LEYUN · SITE SPEC & COMPONENT LIBRARY独立站技术规范手册

EU Responsible Person Information Component Rules

Section:COMPLIANCE BANNER SPEC · Reviewed:2026-11-20 · Template asset

Key takeawayThis section defines the structure template, field dictionary, integration points and compliance boundaries for 「EU Responsible Person Information Component Rules」 in COMPLIANCE BANNER SPEC. Templates are for reference only; verify local regulations and platform rules before launch.

Industries and use cases

  • Sellers whose products fall under EU rules and who must name a responsible person
  • Sites that do not want to repeat the responsible person block on every product page
  • Sites where buyers must be able to find the compliance contact easily
  • Sellers asked by a platform to display compliance information
Template / code snippethtml
<!-- 触发式弹窗:页脚入口 + 产品页入口 -->
<button type="button" class="eu-trigger" data-eu-open>
  EU Responsible Person
</button>

<div class="eu-modal" id="euModal" role="dialog"
     aria-modal="true" aria-labelledby="euModalTitle" hidden>
  <div class="eu-modal-in">
    <button type="button" class="eu-close" data-eu-close
            aria-label="关闭">×</button>
    <h2 id="euModalTitle">EU Responsible Person</h2>
    <p>
      ${companyName} is established outside the European Union.
      The authorised representative designated for the products
      shown on this site is:
    </p>
    <dl class="eu-facts">
      <div><dt>Authorised representative</dt><dd>${repCompany}</dd></div>
      <div><dt>Registered address</dt><dd>${repAddress}</dd></div>
      <div><dt>Contact</dt><dd>${repContact}</dd></div>
      <div><dt>Scope</dt><dd>${repScope}</dd></div>
    </dl>
    <p class="eu-note">
      Declarations of conformity and technical documentation
      are available on request.
    </p>
  </div>
</div>

<script>
(function () {
  var m = document.getElementById('euModal');
  var last = null;
  document.querySelectorAll('[data-eu-open]').forEach(function (b) {
    b.addEventListener('click', function () {
      last = b; m.hidden = false;
      var c = m.querySelector('[data-eu-close]');
      if (c) c.focus();
    });
  });
  m.querySelectorAll('[data-eu-close]').forEach(function (b) {
    b.addEventListener('click', function () { m.hidden = true; });
  });
  document.addEventListener('keydown', function (e) {
    if (e.key === 'Escape' && !m.hidden) {
      m.hidden = true; if (last) last.focus();
    }
  });
})();
</script>
Fields and parameters
Field / parameterTypeDescription and values
Representative nameTextFull legal entity name
Registered addressTextAn address in the EU where service is possible
ContactTextEmail or telephone
ScopeTextProducts and regulations covered
Trigger entry pointElementOne in the footer, one on product pages
Dialog roleARIArole="dialog" aria-modal="true"
Close behaviourInteractionButton plus Esc key, focus returns to the trigger

SEO and structured-data notes

SEO and structured-data checkpoints
The content must be readable by crawlersIf a JS dialog holds content that never appears in the HTML source, compliance information is invisible to whoever checks. Keep a static version on the page as well
Esc must close the dialogIt is a basic usability requirement for dialogs and an accessibility check item
Manage focusFocus moves into the dialog on open and returns to the trigger on close
Both entry points are neededThe footer entry guarantees discoverability, the product page entry provides context
Keep a static footer versionIt satisfies discoverability and retrievability at the same time
State the product scopeA blanket "all products" is easily questioned in an audit

Compliance risk notes

  • A representative must not be fictitious
  • An address where service is impossible must not be used
  • Compliance information must not be hidden in a dialog that is hard to find
  • The stated scope must not exceed the actual mandate
  • The static version must be updated when the content changes

Do not reuse this template verbatim in regulated contexts; verify local regulations and platform rules before going live.

Modification example

<!-- Modification example: JS dialog plus a static footer version in parallel -->
<!-- Dialog-only version: the responsible person is absent from the source -->
<button data-eu-open>EU Responsible Person</button>
<div id="euModal" hidden>...representative details...</div>

<!-- Modified: a static version stays in the footer alongside the dialog -->
<!-- Dialog component (as before) -->
<button type="button" class="eu-trigger" data-eu-open>
  EU Responsible Person
</button>
<div class="eu-modal" id="euModal" role="dialog"
     aria-modal="true" aria-labelledby="euModalTitle" hidden>
  <!-- ... -->
</div>

<!-- Static footer version: visible directly in the HTML source -->
<footer class="ft-eu">
  <h3>EU Responsible Person</h3>
  <p>
    ${companyName} is established outside the European Union.
    The authorised representative designated for the products
    shown on this site is ${repCompany}, ${repAddress}
    (${repContact}).
  </p>
</footer>

<!-- Why two copies:
     the dialog provides the interaction, the static copy provides
     "anyone who opens the source can see it".
     Regulatory checks, platform reviews and third-party audits all read the source.
     A JS-only dialog is effectively absent in those scenarios. -->

FAQ

Can a reviewer see information inside the dialog?
If the content is injected by JS, it is not in the page source. The safer approach is a static version on the page.
Should the dialog open automatically?
Not advisable. Compliance information should be findable on request; forcing a dialog interrupts browsing.
Does every product page need it?
Put a one-line static summary on the page and the full details in the dialog; this keeps the page short while staying discoverable.
What happens when the representative changes?
The dialog, the static footer copy and the compliance page all need updating; make them read from a single data source in the template.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.

Note: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.