Search Engine Indexing

You can enable search engines to index pages in the external facing portal, due to the fact that the light framework page consists of a single frame, and light content is static.

A user agent is an application that is used to browse the Web. Web user agents can be Web browsers or search engine crawlers, or even accessibility products such as screen readers.

When a user agent accesses a Web site, it provides information about itself, such as the brand and version of the browser. When a search engine "reads" portal content, it in effect tries to display the content. However, only user agents supported by the SAP Product Availability Matrix (PAM) can display portal content, so instead of retrieving content and indexing it, the search engine user agent receives an error.

Note Note

For information about supported browsers, see the Product Availability Matrix at service.sap.com/pam.

End of the note.

To allow search engines to access portal pages you need to change the portal's configuration to provide access to all user agents. The SupportedUserAgents property defines which browsers can access the portal. You need to modify this property in all of the pages and iViews that contain content that you want indexed, as well as in all of the portal desktop components. The following components comprise the portal desktop:

Framework Page
All iViews in the Framework Page
Desktop Innerpage
All iViews in the Desktop Innerpage
Framework Layout
Navigation Panel and Content Area Layout

You can modify the SupportedUserAgents property for all of the relevant components simultaneously using the Search and Replace Wizard.

After you have modified the SupportedUserAgents property, you need to perform a number of actions in the NetWeaver Developer Studio to allow search engines to crawl and index portal pages.

Prerequisites

Caution Caution

If used incorrectly, the Search and Replace Wizard can irreversibly damage an entire portal or parts of it. Make sure that you read Multiple Property Replacement and Using the Search and Replace Wizard before working with the wizard.

End of the caution.

To view objects in the wizard's result set, you must have at least administrator read permissions for each object. See Permission Levels.
To be able to change the properties of an object, you must have at least administrator read/write permission for each object.

Procedure

Modify the SupportedUserAgents Property

In the portal, navigate to Content Administration Multiple Property Replacement .
In the Portal Catalog, right-click the folders, worksets, or roles containing content that you want indexed, and select Add <object> to List.
Click Next.
Specify which object types you want to include in the search, and click Next.
Select Search objects by property ID.
- In the Property ID field, type SupportedUserAgents.
- In the New Value field, type (*,*,*).
Click Next.
Select the SupportedUserAgents property and click Next.
Finalize the list of properties and objects you want modified, and click Finish.

Allow Search Engines to Crawl and Index All Portal Pages-Example

Different search engines use different methods to rank content so that it can be found by the search engine.

In the following example, you enable the Google search engine to crawl and index all portal pages. Other search engines may require different configuration.

In the NetWeaver Developer Studio, create a new portal application.

Open the PORTAL-INF/portalapp.xml file, and exchange its contents with the following:

Syntax Syntax

```
<?xml version="1.0" encoding="utf-8"?>
```
```
<application alias="google">
```
```
  <application-config>
```

    <property name="Vendor" value="sap.com"/>

    <property name="SecurityArea" value="NetWeaver.Portal"/>

    <property name="SharingReference" value="com.sap.portal.navigation.navigationtaglibrary"/>

```
  </application-config>
```
```
  <components>
```
```
    <component name="sitemap">
```
```
      <component-config>
```

        <property name="SecurityZone" value="com.sap.portal/no_safety"/>

        <property name="ComponentType" value="jspnative"/>

        <property name="JSP" value="jsp/sitemap.jsp"/>

```
      </component-config>
```
```
      <component-profile>
```

        <property name="EPCFLevel" value="0"/>

        <property name="AuthScheme" value="anonymous"/>

        <property name="NavigationTagLibrary" value="/SERVICE/com.sap.portal.navigation.navigationtaglibrary/taglib/TagLibrary.tld"/>

```
      </component-profile>
```
```
    </component>
```
```
  </components>
```
```
  <services/>
```
```
</application>
```

End of the code.

Create a new file named PORTAL-INF/jsp/sitemap.jsp and paste the following text:

Syntax Syntax

<%@ taglib uri="NavigationTagLibrary" prefix="nav"%>

```
<nav:iterateInitialNavNodes>
```
```
  <nav:recurseNavNodeChildren>
```

    <br><nav:navNodeAnchor navigationMethod="byURL" />

```
  </nav:recurseNavNodeChildren>
```
```
</nav:iterateInitialNavNodes>
```

End of the code.

Upload the new application
Insert the following in the HTML of the Top-Level Navigation iView (com.sap.portal.navigation.toplevel/PORTAL-INF/pagelet /toplevelnavigation.jsp):
Syntax
1. ```
<a href="/irj/servlet/prt/portal/prtroot/google.sitemap" style="position:absolute;top:-99999px">Sitemap</a>
```
End of the code.