SEOMonster Documentation
This version of SeoMonster is fully compatible and was tested with Divi version 3.0.101
Step 1: Install Divi Theme
Once you’ve downloaded the Divi theme package, login to your WordPress website and go to Appearance > Themes.
Find and upload the Divi parent theme and activate it. Next click on the Add New Theme.
Step 2: Install and activate SeoMonster
Click on Upload Theme.
Click on Choose file.
In the downloaded package find and select SEOMonster.zip file, then click on the Install Now button.
Completing the upload, you will need to activate the theme by clicking on the Activate button.
Step 3: Activate your product
To activate your product and get updates please go to Settings > SEOMonster Activation and enter your API Key and API Email.
To see your API Keys please login to your account.
Step 4: Installing plugins
SEOMonster theme requires 2 plugins:
GS Logo Slider and One Click Demo Import.
We have made installation process very simple. After SEOMonster child theme is activated system will ask you to install all missed plugins. Click Begin installing plugins.
On the next screen select all plugins, choose Install from dropdown menu and click Apply.
Step 5: Permalinks setup
It is good SEO practice to set Permalinks Settings to “Post name”.
Go to Settings > Permalinks, select “Post name” and click Save Changes.
Go to Appearance > Import Data Demo, and click on the Import Demo Data button.
Note: This may take even several minutes, depends of internet connection speed. Please be patient.
Elegant Themes
For additional assistance with using the Divi theme framework, Elegant Themes offers free technical support to all their members. Login to your account at Elegant Themes website.
Divi Communities
You can also find support on Facebook or Google+ by posting your questions in the community group:
Divi Theme | Extra Theme | Help & Share.
B3 Multimedia Solutions
For questions or support please visit your account and submit support ticket:
- email optin form fixed
- CSS code optimised
- images import issue fixed
- tested with WP 4.9.8 and Divi 3.13.1