Content Mask vs Each domain a page

Read More & View Demos Here Embed Any Content†‡ Into Your WordPress Website Content Mask allows you to embed any external content onto your own WordPress Pages, Posts, and Custom Post Types. The end result is fairly similar to setting up a Domain Mask, but the content is embedded into the front end of your website and is fully contained inside your WordPress permalink ecosystem. Example: If you built a landing page on landing-page-builder.com/your-landing-page/, you can simply create a new Page on your website at your-site.com/landing-page/ and paste in the URL of your landing page. The Content Mask plugin will then download and cache of copy of your landing page directly on your website, so any visitors that come to your-site.com/landing-page/ will see the landing page you built. This allows you to keep all of your links integrated into your WordPress Website. † Do not use Content Mask to embed any content that you do not own or do not otherwise have license to share, embed, frame, or distribute. Simple 2-Step UI With a simple 2-Step UI, you can embed any external content into your website without any complicated URL Forwarding, DNS Records, or .htaccess rules to mess with. Just enable the Content Mask on any Page, Post, or Custom Post type by clicking on the check mark. Then put in the URL that contains the content you want to embed. It’s that simple! Powerful Embedding and Redirect Options Using the Download method (default) will fetch the content from the Content Mask URL, cache it on your website, and replace the current page request with that content. By default, this cache lasts 4 hours – but it can be changed anywhere from “Never Cache” all the way up to “Cache for 4 Weeks”. Caching prevents the need for additional requests that slow down your site. Using the Iframe method will replace the current page request with a full width/height, frameless iframe containing the host URL. This method is ideal if the URL you want to embed won’t serve scripts, styles, or images to other URLs or IP Addresses. If you use the Download Method, and links or images look broken, you can try the Iframe method instead. Using the Redirect (301) method will simply redirect the visitor to the host URL. Simple Integrated Vistor Tracking In the Content Mask admin panel, you can enable tracking for Content Masked pages. This will allow you to see how many visitors are viewing these links. This is ideal for when you need to track acquisition, such as on a Landing Page. [Views] shows how many times that Content Mask page has been viewed by anybody (even logged in users) [Non-User] shows how many times it’s been viewed by visitors that are not logged in to the website. [Unique] shows how many times it’s been viewed by unique IP addresses. Note: IP addresses are one-way hashed and are not identifiable in any way. Creating a Content Masked Page Using the Content Mask Admin Panel Notes: Do NOT use Content Mask on any content you aren’t explicitly authorized to share or use. Please confirm you’re allowed to utilize and embed the content before embedding any particular URL. Content embedded using the Download method is cached using the WordPress Transients API for 4 hours by default. If the content on the external URL is updated and you would like a fresh copy, you may just click the “Update” button on the Page, Post, or Custom Post Type to refresh the transient, or click the “Refresh” link in the Content Mask Admin panel. You may also change the cache expiration timer per page anywhere from “Never” to “4 weeks”. You may use the Transients Manager plugin to manage transients stored with the Download method. All Content Mask related transients contain the prefix “content_mask-” plus a stripped version of the Content Mask URL, such as “content_mask-httpxhynkcom”. ‡ Your site may be prevented from processing page requests for any reason; Reasons include, but are not limited to: masking unauthorized content, at the request of the masked URL site owner, masking hateful content, masking illegal content, circumventing IP bans, etc. A dual one-way encrypted hash of your masking URL may be used to check for infraction. No identifying information will be used for this check, and no information is saved other than as a transient to prevent unnecessary duplicate checks per site Read More About Content Mask

Easily manage a large number of landing pages or small websites from a single WordPress site. This plugin offers an easy way to map different domains to different landing pages on your WordPress site. Now you can easily maintain a large number of small sites from a single WordPress installation. You don’t have to set anything up, it works out of the box. Just point a domain that you own to your WordPress installation. In WordPress, create a page for that domain. The slug should be the domain name without ‘www’ and with the .’s replaced by hyphens. You can see it working on my own domain: wp-developer.eu, which shows a special page with slug wp-developer-eu on my joerivanveen.com blog (joerivanveen.com/blog/wp-developer-eu is the same). Benefits: Easily reuse and maintain elements like forms on several domains at once. Bring in more traffic using landing pages for multiple domains without hassle. Favicon support for each domain, fallback from child pages to parents. Support for custom post types, e.g. FAQ posts, portfolio posts. The rest of your website keeps working as usual. Caveats: Some themes use webfonts, for them to work a couple of lines are added to your .htaccess, these are clearly marked #ruigehond007 (this is my seventh plugin). If your blog is in a subfolder of the main site (e.g. my-site.com/blog) you need to take an extra step for this to work, see installation tab. Not all custom post types are guaranteed to work as landing page, e.g. WooCommerce products need additional work to be able to access the main cart. If you need more flexibility (and more work) there is WordPress Multisite. I put special care in making the plugin very lightweight, you will notice it has virtually no effect on the speed of your installation. Favicons Switch on with_favicon on the settings page, to allow adding favicons to each landing page (and other pages and posts as well). Supplying the correct favicon(s) is your responsibility, the plugin will not verify their validity. As a rule of thumb I would use a small(ish) SVG for modern browsers, and a 32×32 pixel ICO file as fallback. You may need a plugin to be able to upload ICO and SVG files, since they are blocked by default. .htaccess In case the plugin was not able to update your .htaccess, these are the lines for your .htaccess to make webfonts function properly, you can add them right after ‘#END WordPress’: # BEGIN ruigehond007 Header set Access-Control-Allow-Origin "*" # END ruigehond007 You may need to switch on headers module in your Apache configuration, if it is not already. NGINX NGINX does not process .htaccess files as standard. Best is to add the following to your nginx.conf file: location ~* \.(eot|ttf|otf|woff|woff2)$ { add_header Access-Control-Allow-Origin *; } Alternatively you can switch on processing of .htaccess files in your nginx.conf file. In your hosting environment this may be done by disabling ‘direct delivery’ or something similar.