legacy-knowledge-base
公開されました Jun. 30, 2025

Is there a way for users to visit our site using a custom domain without the search engines show the contents with the link?

written-by

Kenny Back

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

legacy-article

learn-legacy-article-disclaimer-text

Issue

Environment

  • DXP 7.4 Quarterly Release

Resolution

  • This feature is currently under development internally with an expected ETA of next year 2025 (official date TBD). The specifics are not yet concrete, but in short customers will be able configure CDN and WAF settings more autonomously in the future.
  • Now as for options you can implement currently to manage search engine indexing and user access that may help we'd recommend: 
  1. Blocking Search Engines: Configure robots.txt to disallow indexing of *.lfr.cloud URLs. You can add this configuration in the webserver service settings to guide search engines to avoid indexing these URLs.
  2. Redirect Users to Custom Domain: You can configure redirects in the nginx.conf file to direct users accessing the *.lfr.cloud URLs to the custom domain. This customization does require managing updates in your nginx.conf file after each platform release, as configurations may reset.
  3. Workarounds:
    • nginx.conf Customization: As mentioned, you can add rules to your nginx.conf to redirect all traffic from the *.lfr.cloud domain to the custom domain.
    • Custom DNS and SEO Configurations: While the default domain remains as a backup, use SEO settings to prioritize the custom domain and reduce the visibility of the default one in search results.

 

did-this-article-resolve-your-issue

legacy-knowledge-base