Expert knowledge for digital decisions
Which Landing Page is Suitable for a Dynamic QR Code?
Short answer
The QR Code is the Entry Point, Not the Landing Page
With a dynamic QR code, the printed address remains stable while the underlying landing page can be changed. Therefore, the landing page should not be confused with the redirect address. GS1 recommends that a scan leads directly to the expected information – not first to a general homepage, a search form, or through multiple additional clicks.
Five Criteria for a Suitable Page
- Clear Purpose: The heading and first visible content immediately confirm that the correct code has been scanned. A code "User Manual" leads to the appropriate manual; a code "Book Appointment" goes directly to the relevant process. Campaign promises on the print and actual page content must match.
- Mobile and Accessible Presentation: WCAG 2.2 requires for success criterion 1.4.10 that vertically scrolling content is presented at 320 CSS pixels in width without horizontal scrolling, unless a factual exception applies. For success criterion 2.5.8, actionable targets generally have a minimum size of 24 × 24 CSS pixels or a defined spacing exception. Forms need understandable labels; essential information should be presented as real text and not just as an image.
- Stable, Secure Delivery: The page is provided over HTTPS and has a meaningful error state. If a document is temporarily unavailable, the scan should not end on a blank page or in an endless loop.
- Short Path to Content: A redirect is sensible because the target can then be changed without replacing the printed code. However, additional redirect chains increase the number of potential error points. The complete path from the QR code to the final content should therefore be included in the functionality test.
- Controlled Variants: Language, country, or content type can be selected via a resolver. The current GS1-Conformant Resolver Standard provides exactly 1 standard link per identified unit; additional links can be offered by type, language, or context. For normal camera scans, a unique standard target must always be present.
Before publication, the page is tested with a real printed QR code, mobile connection, multiple screen sizes, and activated assistive technologies. Analysis or marketing services are not a prerequisite for a dynamic QR code. If they are used, data protection, consent, and retention must be evaluated separately.
Example from practice
On a machine, it says "Current Maintenance Manual." The scan opens the manual for exactly this model via a stable redirect address. The page works at **320 CSS pixels** in width without horizontal scrolling, offers a download button at least **24 × 24 CSS pixels** in size, and additionally displays the model number, version date, and a contact option in case of an error.
Key facts
- Mobile Presentation
- Reflow at 320 CSS pixels according to WCAG 2.2, success criterion 1.4.10
- Actionable Targets
- generally at least 24 × 24 CSS pixels or permissible spacing exception
- Resolver Standard Target
- exactly 1 default link per identified unit
- Content Path
- 1 direct entry instead of homepage with renewed search
Sources
All external claims are backed by traceable sources.-
01
Web Content Accessibility Guidelines (WCAG) 2.2 World Wide Web Consortium (W3C)
- 02
-
03
GS1-Conformant Resolver Standard 1.2.0 GS1 AISBL