Website profiles · Technology insights · Alternatives

popl.co

Capture leads, scan badges, enrich data, and sync it all to your CRM—at events, conferences, and beyond. Powered by AI and our proprietary data engine, Popl helps companies around the world turn in-person events into a measurable & scalable growth channel.

Paid content
Visit website
Profile views 10 Outbound visits 4 Normal
Popl Full homepage screenshot

At a glance

Category
Artificial Intelligence
Language
English
Paid-content signal
Paid contentObserved
Registered
2019
Hosting
CloudflareInferred
HTTPS certificate trusted
PassedObserved
Last updated

Related questions

More questions →
How Popl's AI Data Enrichment Fills In Missing Lead Information

Popl's AI data enrichment fills gaps in event lead records by matching a scanned badge, business card, or QR code against data from more than 20 data partners, then appending missing contact fields before the record syncs to your CRM. It applies when a captured lead is incomplete or poorly formatted—for example, a badge scan that yields a name and company but no verified email or phone number. Popl describes the enrichment as powered by AI and its proprietary data engine, and positions it as the step between badge scanning and CRM sync.

Where enrichment sits in the capture flow

Popl describes a single sequence for event leads: scan, validate, qualify, enrich, and sync. Enrichment is not a separate product you run later; it is the step that runs after a lead is captured and before the record reaches your CRM. That ordering matters because it means the CRM receives the completed record rather than a partial one that someone has to fix by hand.

The inputs Popl lists for this flow are:

  • Conference badges
  • Business cards
  • LinkedIn QR codes
  • Other contact methods captured through its universal lead scanner

The output is a lead record with missing contact information filled in from Popl's data partners, ready to sync to "any CRM" per the site's description.

The mechanism, step by step

  1. Capture. A team member scans a badge, card, or QR code at the event. The scan produces whatever fields the source contains—often a name, employer, and title, but frequently an incomplete email or no phone number.
  2. Validate and qualify. Popl checks the captured record and assesses it against the team's criteria, so obviously bad or out-of-scope records are handled before enrichment.
  3. Enrich. Popl's AI and data engine match the record against its 20+ data partners and fill in the missing contact fields.
  4. Sync. The completed record is pushed to the connected CRM.

The practical effect: a badge scan that would otherwise be a dead-end record becomes a contactable lead without a rep manually researching it after the show.

Why this matters for event programs

Popl's own page cites the problem enrichment is meant to solve, drawn from what it says are hundreds of customer conversations and verified online sources:

Problem cited Figure
Qualified event leads that never reach the CRM 60%
Collected event leads unusable due to incomplete or poorly formatted data 40–50%
Average time to follow up after a show 9 days
Buyers who choose the first vendor to follow up 8 in 10

Read together, these numbers describe a leaky pipeline: leads are lost before they reach the CRM, a large share of what is collected is unusable, and follow-up is slow enough that competitors who move first win the deal. Enrichment addresses the middle problem directly—incomplete data—which in turn supports faster, more complete follow-up.

What to check before relying on it

  • Which fields get filled. The site says enrichment fills in "all missing contact info," but confirm for your specific use case which fields (email, phone, title, company domain) are populated and how confidence is indicated.
  • CRM compatibility. Popl states records sync to any CRM. Verify your CRM is among the supported integrations and what the sync maps to.
  • Data partner coverage. The 20+ partner figure is stated broadly; coverage can vary by region and industry, so test with a sample of real event leads from your target markets.
  • Pricing and access. Popl links to a pricing page, but the supplied material does not state plan details, limits, or whether enrichment is included at every tier. Check the pricing page before assuming it is part of a given plan.

A concrete scenario

Suppose your team attends a conference and scans 300 badges over two days. Based on Popl's cited 40–50% unusable rate, roughly 120–150 of those records could arrive with missing or malformed contact data. Without enrichment, a rep would need to research each one or discard it. With Popl's flow, those records are matched against partner data and completed before they land in the CRM, so the team can follow up on the full set rather than the clean subset—and do it sooner than the 9-day average Popl cites.

For teams whose event leads routinely arrive incomplete, enrichment is the feature that determines whether the rest of the capture-to-CRM workflow produces usable pipeline. For teams whose scans are already clean, its value depends on how much manual cleanup you currently absorb.

Does Popl Sync Captured Event Leads to CRM Systems?

Yes. Popl is built to sync captured event leads to your CRM. According to Popl's own product description, the platform lets you "capture leads, scan badges, enrich data, and sync it all to your CRM—at events, conferences, and beyond," and it advertises "CRM integrations" and "CRM sync" as core capabilities. The stated goal is to turn in-person events into a measurable, scalable growth channel rather than leaving leads stranded in spreadsheets or notebooks.

What the sync actually covers

Popl's workflow has three connected stages, and CRM sync is the final one:

  1. Capture — scan conference badges, business cards, LinkedIn QR codes, and other contact methods.
  2. Enrich — Popl AI enrichment fills in missing contact details using its data partners, so records are more complete before they reach your CRM.
  3. Sync — push the captured and enriched data into your CRM.

The sync is therefore not just a raw dump of scanned text; it is meant to deliver cleaner, more complete records to your sales system.

Why the sync matters

Popl frames the problem in terms of follow-up speed and data loss. On its site it cites these figures (described as based on customer conversations and verified online sources):

Problem Figure cited by Popl
Qualified event leads that never reach the CRM 60%
Buyers who choose the first vendor to follow up 8 in 10
Average follow-up time after a show 9 days
Collected event leads unusable due to incomplete or poorly formatted data 40–50%

Syncing to the CRM is the mechanism that addresses the first and last rows: leads enter the sales workflow automatically, and enrichment reduces the share of unusable records. Faster follow-up then matters because buyers tend to go with whoever responds first.

Who this fits

CRM sync is most useful if:

  • Your team attends conferences or events and currently re-enters leads manually.
  • Your sales process runs inside a CRM and leads need to arrive there to be worked.
  • You want enriched contact data rather than incomplete badge scans.

If you only need digital business cards and don't run event lead capture through a sales pipeline, the CRM sync capability is less central to your use case.

What to confirm before committing

Popl's public materials state that it syncs to "any CRM" and lists CRM integrations as a feature, but they don't enumerate every supported CRM on the pages reviewed. Before rolling it out:

  • Check that your specific CRM appears in Popl's integration list, or ask Popl directly.
  • Confirm what fields sync and how duplicates are handled in your CRM.
  • Review current plans and pricing on Popl's pricing page, since feature availability can vary by plan.

For the underlying product context, see Popl's site at popl.co; the pricing page is at popl.co/pages/pricing.

What types of badges and contact methods can Popl scan at events?

Popl scans conference badges universally—meaning its scanner is built to work across different events and badge formats rather than requiring a specific show's badge type—and it also captures business cards and LinkedIn QR codes. After any scan, Popl instantly validates, qualifies, enriches, and syncs the contact to your CRM. This applies to in-person events, conferences, and follow-on use beyond the show floor.

What Popl can scan

Based on Popl's product description, the capture surface covers:

Contact method What it means in practice
Conference badges Universal badge scanning designed to work "at every event," not tied to one organizer's format
Business cards Scan a paper card instead of typing details manually
LinkedIn QR codes Capture a prospect's LinkedIn profile code directly from their phone
"And more" Popl positions the scanner as a universal lead scanner, so other scannable contact formats are part of the same flow

The key claim is universal badge scanning—the same tool is meant to handle badges across different conferences and events, which matters if your team attends many shows with different registration vendors.

What happens after a scan

Scanning is only the first step. Popl describes a single flow for every capture type:

  1. Validate — confirm the scanned record is a real, usable contact.
  2. Qualify — apply your criteria so the lead is routed or tagged correctly.
  3. Enrich — Popl AI fills in missing contact info from its 20+ data partners, so incomplete badge data doesn't become a dead lead.
  4. Sync — push the record to your CRM.

This matters because Popl cites that 40–50% of collected event leads are unusable due to incomplete or poorly formatted data, and that 60% of qualified leads met at events never reach a company's CRM. Enrichment and sync are the mechanisms aimed at those two gaps.

Who this fits

  • Teams attending multiple different conferences benefit most from universal badge scanning, since you don't need a separate setup per event.
  • Teams that collect a mix of badges, cards, and LinkedIn codes get one capture flow instead of several tools.
  • Teams with a CRM workflow already in place can use the sync step; Popl states it syncs to "any CRM," though you should confirm your specific CRM is supported before committing.

If your only need is scanning one badge type at a single annual event, the universal-scanning advantage is less relevant—but the enrichment and CRM sync steps still address the follow-up lag Popl highlights (an average of 9 days to follow up after a show).

Practical checks before you rely on it

  • Confirm your CRM is on the supported integration list—"any CRM" is the marketing claim; verify yours.
  • Test enrichment quality on your actual badge data, since enrichment depends on Popl's data partners matching your contacts.
  • Check pricing and plan limits on Popl's pricing page before assuming scan volume or seat counts; the public description does not specify these.
  • Plan the qualification rules in advance so "qualify" at scan time reflects your sales criteria, not a default.

For the broader question of what the platform does end to end, see the related explainer on Popl's AI GTM platform.

What to Consider When Evaluating Popl for Event Lead Capture

Popl is worth a close look if your team attends conferences and trade shows and loses leads between the badge scan and the CRM. Its core promise is a single flow—scan a badge, enrich the record, sync to your CRM—so the evaluation should focus on three things: whether it handles the badges and contact formats your team actually encounters, whether its enrichment and CRM sync fit your sales workflow, and whether it fixes the specific failure points your team has today. The page positions Popl as an "AI GTM platform for in-person events" with universal badge scanning, AI data enrichment from 20+ data partners, and CRM sync.

Start With the Problems Popl Claims to Solve

Popl frames event lead capture as broken and cites these figures (described on the site as based on customer conversations and verified online sources):

Problem Figure cited by Popl
Qualified event leads that never reach the CRM 60%
Buyers who choose the first vendor to follow up 8 in 10
Average follow-up time after a show 9 days
Collected leads unusable due to incomplete or poorly formatted data 40–50%

Use these as a checklist against your own numbers. If your team's leads already land in the CRM quickly and cleanly, the case for switching is weaker. If two or more of these gaps are familiar, the evaluation below matters more.

Coverage: Badges and Contact Methods

Popl says its scanner handles conference badges, business cards, and LinkedIn QR codes, and describes the scanning as "universal"—working at every event. For evaluation, list the events your team attends over the next year and check each one:

  • Badge format: Ask whether the event's badges are standard printed codes or something proprietary. Popl's claim is universal coverage, but confirm against your actual event list rather than assuming.
  • Non-badge contacts: Note how often your team collects business cards or connects via LinkedIn QR codes instead of scanning badges. Popl lists both as supported inputs.
  • Volume and staffing: Consider how many people will scan at peak booth traffic and whether the workflow holds up with multiple staffers on the same event.

Data Enrichment: Does It Fill the Gaps You Have?

Popl says its AI enrichment fills in missing contact information from 20+ data partners, so the team doesn't have to. The evaluation question is whether the fields it completes match what your sales team needs to qualify and route a lead.

Ask for a sample of enriched records from an event similar to yours and check:

  • Which fields arrive complete (email, phone, title, company) and which still require manual work.
  • Whether enrichment happens at scan time or later, since that affects how fast follow-up can start.
  • How your team would handle records that enrichment can't complete.

CRM Sync and Follow-Up Speed

Popl states that captured leads sync to "any CRM." Since the site does not list specific integrations, verify your CRM by name during evaluation rather than inferring support.

The follow-up statistic (9 days average, with most buyers choosing the first vendor to respond) makes sync timing the most consequential question. Confirm:

  • When a scanned lead appears in your CRM—immediately, at the end of the day, or on a batch schedule.
  • What syncs: just contact data, or also event name, booth notes, and lead source for routing and reporting.
  • Who owns follow-up once the record lands, and whether your existing sequences can trigger from synced event leads.

Adoption and Scale Signals

Popl states that 4M+ professionals across 90% of the Fortune 500 trust it and describes itself as the "#1 ranked market leader." These are vendor claims useful as context for maturity, not as proof of fit. Weigh them alongside a trial on one of your real events.

A Practical Evaluation Sequence

  1. Audit your last three events. Count leads collected vs. leads in the CRM, measure average follow-up time, and note how many records were unusable. This gives you a baseline to compare against Popl's cited figures.
  2. Map your badge and contact formats. List the specific events and formats your team will face next year.
  3. Confirm CRM sync details. Name your CRM and ask how and when records arrive, and what fields are included.
  4. Request enriched sample data. Compare completed fields against your qualification criteria.
  5. Pilot at one event. Run Popl alongside your current process and compare capture rate, data completeness, and time-to-first-follow-up.

Where Popl Fits—and Where to Look Closer

Popl is a reasonable fit if your team runs a regular event calendar, your pain is leads falling out of the CRM or slow follow-up, and your CRM is a mainstream system you can confirm support for. Look closer before committing if your events use unusual badge systems, if your qualification depends on custom fields enrichment may not fill, or if your CRM is uncommon—the site does not enumerate integrations, so those cases need direct confirmation. Pricing is listed on Popl's pricing page; review it there against your event volume rather than assuming a cost structure.

What Is Popl and What Does Its AI GTM Platform Do?

Popl is an AI go-to-market (GTM) platform built for in-person events. Its core job is to capture leads at conferences, trade shows, and similar gatherings, scan badges and other contact formats, enrich the data with AI, and sync everything to your CRM. The goal, as Popl describes it, is to turn in-person events into a measurable and scalable growth channel. It fits teams that already invest in events but lack a reliable system for getting those conversations into their CRM quickly and cleanly.

The problem Popl is built around

Popl frames event lead capture as broken, and it backs that up with several statistics drawn from customer conversations and verified online sources:

  • 60% of qualified leads met at events never make it into a company's CRM.
  • 8 out of 10 buyers choose the first vendor to follow up with them after an event.
  • Teams take an average of 9 days to follow up with leads after a show.
  • 40–50% of collected event leads are unusable because the data is incomplete or poorly formatted.

These numbers point to the same failure mode: leads are captured in the moment but lost, delayed, or degraded before they reach the systems where sales can act on them. Popl's pitch is that its platform closes that gap.

What the platform actually does

Popl describes three connected capabilities:

Universal lead capture

Popl scans conference badges, business cards, LinkedIn QR codes, and more. The claim is that scanning works at every event and is not tied to a specific badge format or organizer system. Captured leads are validated and qualified at the point of capture.

AI data enrichment

When contact information is missing or incomplete, Popl's AI enrichment fills in the gaps using what it describes as 20+ different data partners. This directly targets the 40–50% unusable-lead problem: instead of a half-filled record, the team gets a more complete contact profile without manual research.

CRM sync

Enriched leads sync to your CRM, so the record your sales team works from is the same one captured at the event. Combined with faster capture-to-CRM flow, this addresses the follow-up delay that Popl says costs vendors deals.

Popl also lists digital business cards and a universal lead scanner among its offerings, positioning the scanner as a standard, simplified way to collect leads across different events.

Who it is for

Popl says 4M+ professionals across 90% of the Fortune 500 trust the platform. That signals an enterprise and mid-market focus, particularly for organizations running a regular calendar of events. If your team attends or hosts conferences and currently relies on spreadsheets, paper cards, or manual CRM entry afterward, Popl's described workflow maps directly onto that pain.

What to check before deciding

The available material describes capabilities and outcomes but does not include plan details or pricing figures. Popl does publish a pricing page at popl.co/pages/pricing, so check there for current plans and any limits. Before committing, it is worth confirming:

  • Badge compatibility for the specific events you attend most — "universal" is the claim, but your highest-volume shows are the ones that matter.
  • CRM integration with your actual CRM, not just "any CRM" in general.
  • Enrichment coverage in the regions and industries where you operate, since data partners vary in coverage.
  • Data handling terms, especially if you collect leads in jurisdictions with privacy regulations.

If your main problem is leads dying between the show floor and the CRM, Popl's capture-enrich-sync loop is aimed squarely at that. If you only attend one or two small events a year, weigh whether the platform's value justifies adoption against simpler manual processes.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality.

Domain and Registration

Registered in 2019, this domain has about 6 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is GoDaddy.com, LLC, a widely used domain service provider. The domain uses the common .co extension, which is not an independent safety signal.

DNS and Email

The lowest TTL is 30 seconds, supporting rapid record changes at the cost of more frequent lookups. Nameservers are provided by Cloudflare, indicating managed DNS hosting. MX records point to the Google Workspace email service. CAA records restrict which certificate authorities are authorized to issue certificates. No CNAME was found; the observed records resolve directly to addresses.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: Referrer-Policy, Permissions-Policy. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The cf-ray response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. The Server header identifies cloudflare without an exact version.

Technology Stack Analysis

The public page identifies Shopify, Google Tag Manager, Cloudflare without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

The meta description has 256 characters and may be shortened in search results. Twitter Card metadata is configured. JSON-LD includes Organization data, helping describe the organization as an entity. The title has 50 characters, within a common display range. The observed directives allow indexing and link following.

Hosting and Email

DNSCloudflare
HostingCloudflare
EmailGoogle Workspace
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagUnited States Inferred 2606:4700::6812:1256

Registration details

RDAP / WHOIS

RegistrarGoDaddy.com, LLC
Registered2019-11-23
Expires2026-11-23
Domain statusclientDeleteProhibited https://icann.org/epp#clientDeleteProhibited、clientRenewProhibited https://icann.org/epp#clientRenewProhibited、clientTransferProhibited https://icann.org/epp#clientTransferProhibited、clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Nameserversdane.ns.cloudflare.com、paloma.ns.cloudflare.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Apopl.co104.18.18.86300—
Apopl.co104.18.19.86300—
AAAApopl.co2606:4700::6812:1256300—
AAAApopl.co2606:4700::6812:1356300—
MXpopl.coaspmx.l.google.com3001
MXpopl.coalt1.aspmx.l.google.com3005
MXpopl.coalt2.aspmx.l.google.com3005
MXpopl.coalt3.aspmx.l.google.com30010
MXpopl.coalt4.aspmx.l.google.com30010
NSpopl.codane.ns.cloudflare.com86400—
NSpopl.copaloma.ns.cloudflare.com86400—
TXTpopl.coMS=ms4486151130—
TXTpopl.coVtpTPxVrBznNvBKQuR7gHewIB-3lkWo5wOB8Vr82ucw30—
TXTpopl.coanthropic-domain-verification-n7ecga=ZqqzE5WkeQXy5uZUZUUUIvwMu30—
TXTpopl.coapple-domain-verification=402lzhSVclARMB5z30—
TXTpopl.cobeautifulai-site-verification=b61ff841-1e69-4b5f-877d-f488eb2b59d330—
TXTpopl.cofirebase=poplco30—
TXTpopl.cogoogle-site-verification=0mro2sarMa3HGeieT0l8OnoLR8nQFQ8Xvlc6RMY0qbo30—
TXTpopl.cogoogle-site-verification=52jUCdOi8vTDTKKo8O-rSf5vRXQstxOY6aLdHFnjw9U30—
TXTpopl.cogoogle-site-verification=C2qX4cuL8qzmyfz3n_IPQdhoMRYhkTWdq3neNDft9bg30—
TXTpopl.cogoogle-site-verification=yOKha6f6hBKqF306O74A4Poc3FKpkHP5-RlQyk7wduI30—
TXTpopl.cohibp-verify=dweb_z9ndy4dkygdps8vdnxxao8uk30—
TXTpopl.cohubspot-developer-verification=MWMxMGYwNjUtMDMzYS00YWM1LWE3YTYtMmMwZDhhNWJkNDI530—
TXTpopl.cohubspot-developer-verification=NzNjOTVmODItYjRhMC00YWU1LTg3ODUtNWM2NjA3YWViZWJh30—
TXTpopl.cohubspot-developer-verification=ODU5YWRhZGUtN2U2Zi00ZDIwLWFkZDUtZjA3NjBhZThiODVh30—
TXTpopl.coklaviyo-site-verification=PdFqYJ30—
TXTpopl.colinkedin-site-verification=c7302a69-f9ed-4e9a-b7dd-7a5c070c127330—
TXTpopl.copardot1013852=0802acf6e11e3532da1ce3fceecd31396879a8fc8e3295b431ed286cdf4bebe430—
TXTpopl.copardot1013852=57d3b1fa947b207bd8449a079720b8b01d8548968b9bdf822c2b46480106d7e730—
TXTpopl.cov=spf1 include:_spf.google.com include:sendgrid.net include:19933619.spf02.hubspotemail.net -all30—
TXTpopl.cov=verifydomain MS=919039130—
CAApopl.co0 issue "amazonaws.com"300—
CAApopl.co0 issue "comodoca.com"300—
CAApopl.co0 issue "digicert.com; cansignhttpexchanges=yes"300—
CAApopl.co0 issue "globalsign.com"300—
CAApopl.co0 issue "letsencrypt.org"300—
CAApopl.co0 issue "pki.goog; cansignhttpexchanges=yes"300—
CAApopl.co0 issue "ssl.com"300—
CAApopl.co0 issuewild "amazon.com"300—
CAApopl.co0 issuewild "comodoca.com"300—
CAApopl.co0 issuewild "digicert.com; cansignhttpexchanges=yes"300—
CAApopl.co0 issuewild "letsencrypt.org"300—
CAApopl.co0 issuewild "pki.goog; cansignhttpexchanges=yes"300—
CAApopl.co0 issuewild "ssl.com"300—
DMARC_dmarc.popl.cov=DMARC1;p=quarantine;rua=mailto:[email protected],mailto:[email protected];ruf=mailto:[email protected]300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectpopl.co
IssuerLet's Encrypt
Valid until2026-12-24T15:14 · Remaining when checked: 59 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
content-languageen-US
cache-controlprivate, max-age=0, must-revalidate
servercloudflare
strict-transport-securitymax-age=7889238
content-security-policyblock-all-mixed-content; frame-ancestors 'none'; upgrade-insecure-requests;
x-frame-optionsDENY
x-content-type-optionsnosniff
set-cookieRedacted

Identified technologies

ShopifyGoogle Tag ManagerCloudflare

Pages, Search and Sharing

Meta descriptionCapture leads, scan badges, enrich data, and sync it all to your CRM—at events, conferences, and beyond. Powered by AI and our proprietary data engine, Popl helps companies around the world turn in-person events into a measurable & scalable growth channel.
Canonical URLhttps://popl.co/
LanguageEnglish (default)
Twitter Cardsummary
All bots 23 allowed · 40 disallowed
  • Allow/
  • Allow/products/account
  • Allow/products/orders
  • Allow/products/checkout
  • Allow/*/products/account
  • Allow/*/products/orders
  • Allow/*/products/checkout
  • Allow/collections/account
  • Allow/collections/orders
  • Allow/collections/checkout
  • Allow/*/collections/account
  • Allow/*/collections/orders
  • Allow/*/collections/checkout
  • Allow/pages/checkout
  • Allow/*/pages/checkout
  • Allow/blogs/*account
  • Allow/blogs/*orders
  • Allow/blogs/*checkout
  • Allow/*/blogs/*account
  • Allow/*/blogs/*orders
  • Allow/*/blogs/*checkout
  • Allow/account/login
  • Allow/*/account/login
  • Disallow/admin
  • Disallow/cart/
  • Disallow/*/cart/
  • Disallow/checkout
  • Disallow/*/checkout
  • Disallow/checkouts/
  • Disallow/*/checkouts/
  • Disallow/orders
  • Disallow/*/orders
  • Disallow/account
  • Disallow/*/account
  • Disallow/25753157735
  • Disallow/cdn/wpm/*.js
  • Disallow/services
  • Disallow/sf_*
  • Disallow/cart.js
  • Disallow/*/cart.js
  • Disallow/recommendations/products
  • Disallow/*/recommendations/products
  • Disallow/collections/*sort_by*
  • Disallow/*/collections/*sort_by*
  • Disallow/collections/*+*
  • Disallow/collections/*%2B*
  • Disallow/collections/*%2b*
  • Disallow/*/collections/*+*
  • Disallow/*/collections/*%2B*
  • Disallow/*/collections/*%2b*
  • Disallow/collections/*filter*&*filter*
  • Disallow/*/collections/*filter*&*filter*
  • Disallow/blogs/*+*
  • Disallow/blogs/*%2B*
  • Disallow/blogs/*%2b*
  • Disallow/*/blogs/*+*
  • Disallow/*/blogs/*%2B*
  • Disallow/*/blogs/*%2b*
  • Disallow/*?*ls=*&ls=*
  • Disallow/*?*ls%3*ls%3*
  • Disallow/*?*oseid=*
  • Disallow/*?*preview_theme_id=*
  • Disallow/*?*preview_script_id=*
adsbot-google 12 allowed · 10 disallowed
  • Allow/products/
  • Allow/*/products/
  • Allow/collections/
  • Allow/*/collections/
  • Allow/pages/
  • Allow/*/pages/
  • Allow/blogs/
  • Allow/*/blogs/
  • Allow/pages/checkout
  • Allow/*/pages/checkout
  • Allow/blogs/*checkout
  • Allow/*/blogs/*checkout
  • Disallow/checkout
  • Disallow/*/checkout
  • Disallow/checkouts/
  • Disallow/*/checkouts/
  • Disallow/orders
  • Disallow/*/orders
  • Disallow/services
  • Disallow/sf_*
  • Disallow/25753157735
  • Disallow/cdn/wpm/*.js

Recent Updates

  • Website images
  • Screenshots
  • Network details
  • Website Technologies
  • Pages and Search Information
  • HTTP Response Information
  • TLS and certificates
  • DNS Information
  • Domain Registration
  • Website profile
  • Website Description
  • Website Name
  • Website profile
  • Website Description
  • Website Name

User reviews (0)

  • No reviews yet.