Restricting by a visitor's location

Locksmith can help you restrict access by automatically detecting the location of the IP address of a visitor. The location condition supports many type of locations including:

  • Regions (eg: North America, Asia, Antarctica)
  • Countries (eg: Australia, Germany, Nauru)
  • Provinces/States (eg: Texas, Nova Scotia, Sikkim)
  • Cities (eg: Montreal, Chicago, Tokyo)
  • Towns (eg: Český Krumlov, Santa Maddalena)

Giving access to locations

Once you've created your lock, choose the Location key:

Next, in the key configuration box,  search for the location: 

Click the name of the area to add it to the key. Feel free to add additional locations: 

Save the key, and you're all set. Those locations will be given access to your locked content, but everyone else around the world won't.

Hiding FROM locations

To make sure some locations don't see your locked content, you'll use the same method. 

Add your location(s) to the key like normal, but this time click the "invert" box in the upper right of the key box: 

The result here is that customers around the world can get access to your locked content, all except for those in that location. 

Important limitations

Shipping addresses: Locksmith can only protect the frontend of your Online Store, and cannot extend its protections to Checkout. So, this does not prevent customers who have IP addresses located in an allowed location from choosing a specific shipping address that is in a blocked location at checkout. Locksmith is not able to control shipping destinations during checkout.

Search engine optimization: If you're using the locations key when locking your entire store, or products on your store, this will strongly effect your SEO for any pages that are covered by these locks. This is because search engines will no longer be able to index any pages covered by the lock. Check out the Search Engines and SEO guide for more information.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.