DOCSLIB.ORG

Endeca Sitemap Generator Developer's Guide Version 2.1.1 • March 2012

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Endeca Sitemap Generator Developer's Guide Version 2.1.1 • March 2012 Endeca Sitemap Generator Developer's Guide Version 2.1.1 • March 2012 Contents Preface.............................................................................................................................7 About this guide............................................................................................................................................7 Who should use this guide............................................................................................................................8 Conventions used in this guide.....................................................................................................................8 Contacting Oracle Endeca Customer Support..............................................................................................8 Chapter 1: Introduction..............................................................................9 About sitemaps.............................................................................................................................................9 About the Endeca Sitemap Generator..........................................................................................................9 Chapter 2: Installing the Endeca Sitemap Generator............................11 System requirements..................................................................................................................................11 Installing the Sitemap Generator................................................................................................................12 Package contents and directory structure...................................................................................................12 Chapter 3: Running the Sitemap Generator...........................................15 Running the Sitemap Generator from the command line............................................................................15 Standard output..........................................................................................................................................15 File outputs.................................................................................................................................................16 Index file..............................................................................................................................................16 Detail files............................................................................................................................................17 Navigation files....................................................................................................................................17 Search term files..................................................................................................................................18 Static pages files.................................................................................................................................18 Chapter 4: Configuring the Sitemap Generator.....................................21 Configuration files.......................................................................................................................................21 The main configuration file..........................................................................................................................21 MDEX Engine configuration.................................................................................................................23 The query field list...............................................................................................................................23 The navigation page spec list..............................................................................................................24 The template configuration file....................................................................................................................25 About tag replacement........................................................................................................................26 Replacement tags for INDEX_LINK.....................................................................................................26 Replacement tags for DETAIL_LINK...................................................................................................27 Replacement tags for NAVIGATION_LINK..........................................................................................27 Replacement tags for SEARCH_LINK.................................................................................................28 Replacement tags for STATIC_PAGE_LINK........................................................................................28 The search terms configuration file.............................................................................................................28 The static pages configuration file..............................................................................................................29 The URL formatting configuration file.........................................................................................................30 Chapter 5: Troubleshooting and Performance.......................................31 Common errors...........................................................................................................................................31 Performance information.............................................................................................................................33 Chapter 6: Implementing the Sitemap Generator in Production..........35 About validating sitemaps...........................................................................................................................35 About moving sitemap files to production...................................................................................................35 Notifying search engines of a sitemap location..........................................................................................36 Notifying search engines of an updated sitemap .......................................................................................36 iii Copyright and disclaimer Copyright © 2003, 2012, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. UNIX is a registered trademark of The Open Group. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. This software or hardware and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services. Rosette® Linguistics Platform Copyright © 2000-2011 Basis Technology Corp. All rights reserved. Teragram Language Identification Software Copyright © 1997-2005 Teragram Corporation. All rights reserved. v Preface Oracle Endeca's Web commerce solution enables your company to deliver a personalized, consistent customer buying experience across all channels — online, in-store, mobile,
Load more

Recommended publications
  • Intro to Google for the Hill
    Introduction to A company built on search Our mission Google’s mission is to organize the world’s information and make it universally accessible and useful. As a first step to fulfilling this mission, Google’s founders Larry Page and Sergey Brin developed a new approach to online search that took root in a Stanford University dorm room and quickly spread to information seekers around the globe. The Google search engine is an easy-to-use, free service that consistently returns relevant results in a fraction of a second. What we do Google is more than a search engine. We also offer Gmail, maps, personal blogging, and web-based word processing products to name just a few. YouTube, the popular online video service, is part of Google as well. Most of Google’s services are free, so how do we make money? Much of Google’s revenue comes through our AdWords advertising program, which allows businesses to place small “sponsored links” alongside our search results. Prices for these ads are set by competitive auctions for every search term where advertisers want their ads to appear. We don’t sell placement in the search results themselves, or allow people to pay for a higher ranking there. In addition, website managers and publishers take advantage of our AdSense advertising program to deliver ads on their sites. This program generates billions of dollars in revenue each year for hundreds of thousands of websites, and is a major source of funding for the free content available across the web. Google also offers enterprise versions of our consumer products for businesses, organizations, and government entities.
    [Show full text]
  • Web Site Metadata
    Web Site Metadata Erik Wilde and Anuradha Roy School of Information UC Berkeley Abstract. Understanding the availability of site metadata on the Web is a foundation for any system or application that wants to work with the pages published by Web sites, and also wants to understand a Web site’s structure. There is little information available about how much information Web sites make available about themselves, and this paper presents data addressing this question. Based on this analysis of available Web site metadata, it is easier for Web-oriented applications to be based on statistical analysis rather than assumptions when relying on Web site metadata. Our study of robots.txt files and sitemaps can be used as a starting point for Web-oriented applications wishing to work with Web site metadata. 1 Introduction This paper presents first results from a project which ultimately aims at pro- viding accessible Web site navigation for Web sites [1]. One of the important intermediary steps is to understand how much metadata about Web sites is made available on the Web today, and how much navigational information can be extracted from that metadata. Our long-term goal is to establish a standard way for Web sites to expose their navigational structure, but since this is a long-term goal with a long adoption process, our mid-term goal is establish a third-party service that provides navigational metadata about a site as a service to users interested in that information. A typical scenario would be blind users; they typically have difficulties to navigate Web sites, because most usability and accessibility methods focus on Web pages rather than Web sites.
    [Show full text]
  • SEO SERVICES. Bad Penny Factory Is a Digital Narration and Design Agency, Founded in Oklahoma and Grown and Nurtured in the USA
    SERVICES. SEO Bad Penny Factory is a digital narration and design agency, founded in Oklahoma and grown and nurtured in the USA. Bad Penny Factory is an award winning agency with prestigious accolades recognized the world over. COMPANY SEO SERVICES SEO PACKAGES Search Engine Optimization (SEO) uses specific keywords to help to boost the number of people that visit your website. How does it work? It targets users that are most likely to convert on your website and takes them there. Our SEO also packages ensure long-term keyword connections to ensure secured ranking placements on search results pages. $500/Month $750/Month • 9, 12 and 18 Month Terms • 9, 12 and 18 Month Terms • One-Time $275 Setup Fee • One-Time $375 Setup Fee • Services for 1 Website • Services for 1 Website // Entry Packages with Scalable Options Bad Penny Factory SEO Packages Aggressive Market Leader Number of Keyphrases Optimized Up to 80 Up to 150 Keyphrase Research and Predictive Selection X X Meta Tags (titles and descriptions) X X Optimization of Robots.txt and GoogleBot Crawls X X Creation and Registrations of Sitemap.xml X X Google My Business Optimization X X Custom Client Reporting Dashboards with Data Views X X Local Search Optimization X X View and Track Competitor Data and Search Rankings X X Original Blog Post Creation 2 Assets Per Month 4 Assets Per Month Link Repair and Building X X Add-On Domain Selection and Buying 2 Assets 5 Assets Media Library and Image Collection Optimization Up to 80 Up to 300 Voice Search Optimization X X Page Speed Audit X X Creation
    [Show full text]
  • Prior Experience Education Skills
    DANNY BALGLEY [email protected] · www.DannyBalgley.com EXPERIENCE AT GOOGLE Google · Google Maps UX designer for Google Maps on the Local Discovery team working on feature enhancements for UX Designer lists and personal actions (saving & sharing.) Recent projects include high profile updates to the Dec 2017 – Present app mentioned at Google I/0 2018 including enhanced editorial lists and “Group Planning” a collaborative tool for planning a meal with friends. Current responsibilities include prototyping, rapid iteration and working with researchers and leads to evolve Google Maps from beyond just a navigation tool to a dynamic discovery app for finding places and things to do. Google · Local Search Worked on the design team tasked with modernizing placesheet from both a feature and Visual & UX Designer framework perspective, making data more accessible, organized, dynamic and contextual. This Nov 2016 – Dec 2017 involved crafting new components and scalable patterns in a contemporary way that could gracefully extend across 30+ verticals for over 250M distinct places. Responsibilities included working across PAs for UI alignment, conducting iterative research to gauge feature success and chaperoning UX updates through weekly partner team syncs. Google · Zagat Web Visual and UX designer on the small team tasked with reimagining the modern web presence for Visual & UX Designer Zagat. This required wire-framing, sitemaps, user journeys, heuristics and prototypes all while Aug 2016 – Nov 2016 working with research & content teams on both strategy and product perception. Worked closely with eng team on implementation and polish of adaptive designs and features such as the robust search and refinement experience for finding the perfect restaurant.
    [Show full text]
  • SEO 101: a V9 Version of Google's Webmaster Guidelines
    SEO 101: A V9 Version of Google's Webmaster Guidelines March 2016 The Basics Google’s Webmaster Guidelines have been published for years, but they recently underwent some major changes. They outline basics on what you need to do to get your site indexed, ranked and not tanked. But what if I don’t wanna follow the guidelines? A rebel, eh? Well, some of the guidelines are best practices that can help Google crawl and index your site - not always required, but a good idea. Other guidelines (specifically quality guidelines), if ignored, can earn you a hefty algorithmic or manual action - something that can lower your ranking or get you kicked out of the SERPs entirely. Google breaks the guidelines up into three sections - we’ll do the same. ● Design and content guidelines ● Technical guidelines ● Quality guidelines Before doing anything, take a gut check: ● Would I do this if search engines didn’t exist? ● Am I making choices based on what would help my users? ● Could I explain this strategy to my competitor or my mama and with confidence? ● If my site went away tomorrow, what would the world be missing? Am I offering something unique and valuable? 1 Updated March 2016 Now, Let’s Get Your Site Indexed Make Sure Your Site is Crawlable ● Check www.yourdomain.com/robots.txt ● Make sure you don’t see: User-agent: * Disallow: / ● A robots.txt file that allows bots to crawl everything would look like: User-agent: * Disallow: ● Learn more! Make Sure You’re Allowing Google to Include Pages in their Index ● Check for and remove any meta tags that noindex pages: <meta name="robots" content="noindex" /> ● Do a Fetch as Google in Search Console and check the header for x-robots: noindex directives that need to be removed X-Robots-Tag: noindex ● Learn more! 2 Updated March 2016 Submit Your Site to Google When ready, check out Google’s options for submitting content.
    [Show full text]
  • Get Discovered: Sitemaps, OAI and More Overview
    Get Discovered: Sitemaps, OAI and more Overview Use Cases for Discovery Site map SEO OAI PMH Get Discovered? Nah. Get Discovered! This is what I’m talking about! Discovery is all about being able to find our digital assets for RE-USE Metrics for Discoverability Mission Statements from the Wild University of Western Sydney: Research Direct Mission Statements from the Wild University of Prince Edward Island: Island Scholar How do I Start? Understand the metrics and what matters the most Standard modules in the latest version of Islandora will help Any site administrator can enable and configure them Sitemap XML Site map “ tells the search engine about the pages in a site, their relative importance to each other, and how often they are updated. [...] This helps visitors and search engine bots find pages on the site” (Wikipedia, 2014). Islandora XML Sitemaps creates these maps for your repository. Add URLs for Islandora objects to the XML sitemap module's database as custom links. When the XML sitemap module creates its sitemap it will include these custom links. http://www.islandora.ca/content/updates-islandora-7x-13-release https://github.com/Islandora/islandora_xmlsitemap Search Engine Optimization SEO “is the process of affecting the visibility of a website or a web page in a search engine's "natural" or un-paid ("organic") search results. [...] SEO may target different kinds of search, including [...] academic search.” (Wikipedia, 2014). An example of an academic search is Google Scholar. ● Islandora Google Scholar Configuration (URL/admin/islandora/solution_pack_config/scholar)
    [Show full text]
  • Javascrip Alert Document Lastmodified
    Javascrip Alert Document Lastmodified High-octane and misanthropical Osbourne combine her Colossian whooshes blithesomely or mad cumulatively, is Costa transcendent? Exanthematic and wieldiest Raoul remarks her earlaps thalwegs mainline and reappraises dustily. Christ never drubbings any interdiction jazz cryptically, is Laurent resourceless and rhematic enough? All smartphones in chrome, they javascrip alert document lastmodified an office and parse methods are protected by js by all the references. Open your error message or if they paste into a report by a new web javascrip alert document lastmodified by using firefox? DocumentlastModified Web APIs MDN. Examples javascrip alert document lastmodified links. When the page for the instructions mentioned the following methods, the top javascrip alert document lastmodified attachments, they use the most recent the purpose. Generally this advanced data javascrip alert document lastmodified stated? Javascriptalertdocumentlast modified too old my reply Sharon 14 years ago Permalink I squint trying to find a grudge to see reading a website was last updated. Use JavaScript to smoke whether a website is static or. This is very javascrip alert document lastmodified jesus essay to include individual contributors, so this api that one qt bot, but not underline, or pick up and manipulating text? Knowing when you javascrip alert document lastmodified by clicking on a webpage source types and execute a website? If there have to do javascrip alert document lastmodified space removal. Http sites to access their users javascrip alert document lastmodified wrong to update date that it a file from being submitted from wayback machine for any highlighted text. Do you should review at the title first indexed date in college of the world wide javascrip alert document lastmodified an anonymous function? Use of a website you want to javascrip alert document lastmodified in.
    [Show full text]
  • SDL Tridion Docs Release Notes
    SDL Tridion Docs Release Notes SDL Tridion Docs 14 SP1 December 2019 ii SDL Tridion Docs Release Notes 1 Welcome to Tridion Docs Release Notes 1 Welcome to Tridion Docs Release Notes This document contains the complete Release Notes for SDL Tridion Docs 14 SP1. Customer support To contact Technical Support, connect to the Customer Support Web Portal at https://gateway.sdl.com and log a case for your SDL product. You need an account to log a case. If you do not have an account, contact your company's SDL Support Account Administrator. Acknowledgments SDL products include open source or similar third-party software. 7zip Is a file archiver with a high compression ratio. 7-zip is delivered under the GNU LGPL License. 7zip SFX Modified Module The SFX Modified Module is a plugin for creating self-extracting archives. It is compatible with three compression methods (LZMA, Deflate, PPMd) and provides an extended list of options. Reference website http://7zsfx.info/. Akka Akka is a toolkit and runtime for building highly concurrent, distributed, and fault tolerant event- driven applications on the JVM. Amazon Ion Java Amazon Ion Java is a Java streaming parser/serializer for Ion. It is the reference implementation of the Ion data notation for the Java Platform Standard Edition 8 and above. Amazon SQS Java Messaging Library This Amazon SQS Java Messaging Library holds the Java Message Service compatible classes, that are used for communicating with Amazon Simple Queue Service. Animal Sniffer Annotations Animal Sniffer Annotations provides Java 1.5+ annotations which allow marking methods which Animal Sniffer should ignore signature violations of.
    [Show full text]
  • Efficient and Flexible Access to Datasets on the Semantic
    Semantic Sitemaps: Efficient and Flexible Access to Datasets on the Semantic Web Richard Cyganiak, Holger Stenzhorn, Renaud Delbru, Stefan Decker, and Giovanni Tummarello Digital Enterprise Research Institute (DERI), National University Ireland, Galway Abstract. Increasing amounts of RDF data are available on the Web for consumption by Semantic Web browsers and indexing by Semantic Web search engines. Current Semantic Web publishing practices, however, do not directly support efficient discovery and high-performance retrieval by clients and search engines. We propose an extension to the Sitemaps protocol which provides a simple and effective solution: Data publishers create Semantic Sitemaps to announce and describe their data so that clients can choose the most appropriate access method. We show how this protocol enables an extended notion of authoritative information across different access methods. Keywords: Sitemaps, Datasets, RDF Publishing, Crawling, Web, Search, Linked Data, SPARQL. 1 Introduction Data on the Semantic Web can be made available and consumed in many dif- ferent ways. For example, an online database might be published as one single RDF dump. Alternatively, the recently proposed Linked Data paradigm is based on using resolvable URIs as identifiers to offer access to individual descriptions of resources within a database by simply resolving the address of the resources itself [1]. Other databases might offer access to its data via a SPARQL endpoint that allows clients to submit queries using the SPARQL RDF query language and protocol. If several of these options are offered simultaneously for the same database, the choice of access method can have significant effects on the amount of networking and computing resources consumed on the client and the server side.
    [Show full text]
  • Copy of Google Sitemap App
    Copy of Google Sitemap app The Google Sitemap app creates an XML Sitemap file that lists URLs for each page. Sitemaps are used to tell search engines which pages they should index. This improves search engine optimization (SEO) by ensuring that all site pages are found and indexed. This is particularly important for sites that use dynamic access to content such as Adobe Flash and for sites that have JavaScript menus that do not include HTML links. Where navigation is built with Flash, a search engine will probably find the site homepage automatically, but may not find subsequent pages unless they are provided in a Google Sitemap format. Note that using Google Sitemaps does not guarantee that all links will be crawled, and even crawling does not guarantee indexing. Nevertheless, a Google Sitemap is still the best insurance for visibility in search engines. Webmasters can include additional information about each URL, such as when it was last updated, how often it changes, and how important it is in relation to other URLs in the site. Google Sitemaps adhere to the Sitemaps protocol and are ready to be submitted to search engines. Creating a sitemap Editing sitemap entries Editing virtual URI entries Publishing Viewing the sitemap Adding to robots.txt file Submitting to search engines Creating a sitemap To create a new sitemap, in Google Sitemaps (browser subapp): Click Add sitemap. You can also arrange your sitemaps in folders. In Site Map Properties: Name: The internal name of the sitemap. URI: The URI that renders the sitemap. Include Virtual URIs: Select to include any defined virtual URIs.
    [Show full text]
  • XML Google Sitemap User Guide
    XML Google Sitemap Magento Extension User Guide Official extension page: XML Google Sitemap User Guide: XML Google Sitemap Page 1 Support: http://amasty.com/contacts/ Table of contents: 1. Google Sitemap Settings……………….……………………………………………….…………...3 2. Google Sitemap General Settings……..…….………….……………………………………….4 3. Google Sitemap Product Settings.………………………………………………………..……..5 4. Google Sitemap Category Settings……………………………….……………………………..6 5. Google Sitemap Pages Settings…………………………………………………...………..……7 6. Google Sitemap. Tags………….………..……………………………..……………….……..……8 7. Google Sitemap. Extra Links………………………………………………………………………9 User Guide: XML Google Sitemap Page 2 Support: http://amasty.com/contacts/ 1. Google Sitemap Settings Please go to Admin panel -> CMS -> SEO Toolkit -> Google Sitemaps To create a new sitemap, click the Add New Sitemap button Specify the number of days before orders get archived. Choose order statuses which should be archived. You can select multiple statuses at a time. Here you can see all google sitemaps, generated with the extension. User Guide: XML Google Sitemap Page 3 Support: http://amasty.com/contacts/ 2. Google Sitemap General Settings Specify path for XML sitemap Specify max items per file and max file size. Google requirements for XML sitemap: - No more than 50,000 URLs in a sitemap ; - - Size no larger than 50MB ; User Guide: XML Google Sitemap Page 4 Support: http://amasty.com/contacts/ 3. Google Sitemap Product Settings Specify whether to include products into XML sitemap. Set ‘Yes’ to include product images into XML sitemap. Specify priority to tell Google which pages are the most important on your site. Specify how often content on Set ‘Yes’ to include the product pages date when the page was are being last modified. updated.
    [Show full text]
  • SEO for Mobile How Do You Let Google Know About the Mobile Version of Your Site? (Onsite Optimisation)
    SEO for Mobile How do you let Google know about the mobile version of your site? (Onsite Optimisation) As a follow-up to the previous post on “Why care about SEO for Mobile” (http://toolbox.schibsted.com/?p=13178), we will start with some onsite optimisation tactics mostly technical with some similarities on the desktop optimisation. Before we think of how we will rank significantly on the mobile search engines, it is a great need if we think first of how do we appear on search engines. Here we will cover actions that will affect the indexation of our mobiles urls and be discoverable by the search engines. #1 Submission to Google Webmaster tools Verify Your Mobile Site in Google Webmastertools, the same way as how you verify on the desktop version. This works for mobile sites with separate mobile urls and it’s very helpful for getting data specifically about the mobile site. Just log on to your google webmaster tools account and select the add site. There you will see the procedures provided by Google on how to verify your site. Webmastertools login page: http://goo.gl/ZIRWE #2 Mobile URLs Two types of mobile website: Responsive Web design Sites that use responsive web design, i.e. sites that serve all devices on the same set of URLs, with each URL serving the same HTML to all devices and using just CSS to change how the page is rendered on the device. Websites with Separate Mobile URLs (Used by some SCM websites) In this configuration, each desktop URL has an equivalent different URL serving mobile- optimized content.
    [Show full text]