Creating a website in APEX might be an easy tasks for an experienced developer, but what about making your website “Google-friendly”? Or any other “Search-engine-friendly”? By default, APEX applications have very little “out-of-the-box” features for Search Engine Optimization (SEO). The URL links look messy, you have no default description or keywords meta-tag. But all this can be fixed by following these simple rules. These rules were enforced on the old versio of www.apexninjas.com (built on APEX NinjaBlog Platform) and have proven to work (over 50% of our daily hits come from Google) and are basically simple SEO guidelines:
1. Make sure each of your site pages has a distinct name. Do not look at an APEX page (which is an application page) as a webpage. They might be same, but might also not.
2. Insert “description” and “keywords” meta tags in each of your pages’ HTML header
3. Create a sitemap and register it to Google Webmaster Tools application. Eliminate the session id from the URLs.
4. Follow basic SEO rules: content is king, use H1 and H2 tags for titles, use bold text for emphasis, add alt tags to your pictures and do not repeat or copy content from other web resources.
Importing whole applications vs. importing pages and components
This article describes the import of APEX pages and shared components. This operation is relevant when deploying modifications from the development environment to the production environment.
One of the most used and simple ways of transferring modifications to the APEX application into another environment is a complete recreation of the workspace and application. The steps are not subject of this document, but the major drawbacks from this method are:
– The workspace in the destination environment is deleted, along with all associated applications, and recreated
– The applications from the workspace need to be imported again, even if we only want to deploy only one of the applications from the previously deleted workspace
– All these operations take time and make the applications unavailable during the import
So, a simpler way is to apply modifications to an application stored in a different workspace, component by component and page by page, if the total number of new/modified pages or components is not close to the total number of components and pages in the application (in this case, a full application import will be more suitable).
The main concern and the scope of this document is importing pages or shared components from a development environment to a production environment. Usually, in the production mode we have all applications installed in runtime mode and the APEX installation itself does not have an Admin section, so all operations must be done using PLSQL and SQL scripts.