# US 9,436,765 B2 · System for deep linking and search engine support for web sites integrating third party application and components > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 9,436,765 B2 - Document ID: US9436765B2 - Status: Granted - Kind: B2 - Application number: 14/053,614 - Filed: 2013-10-15 - Published: 2014-04-17 - Granted: 2016-09-06 - Earliest claimed: 2012-10-15 - Assignees: Wix.com Ltd. - Applicants: Wix.com Ltd. - Inventors: Yoav Abrahami; Uri Tagger - Web page: https://patentgrep.com/patent/US9436765B2 ## CPC - G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links} - G06F 16/951: Indexing; Web crawling techniques - G06F 16/955: using information identifiers, e.g. uniform resource locators [URL] - G06F 16/972: {Access to data in other repository systems, e.g. legacy data or dynamic Web page generation} - G06F 40/143: Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD] - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A system and method for a website including a detector to detect and analyze at least the source of at least one incoming request and a uniform resource locator (URL) handler to parse the incoming request. The system and method also include a coordinator with access to at least one third party application to coordinate between the URL handler and at least one third party application and at least one renderer to receive the output of the coordinator and the detector and to generate at least one of a regular website page, an indexing adapted page and a sitemap according at least to the source of the incoming request. ## Claims ### Claim 1 A website server, said server implemented on at least one processor and a memory, the system comprising: a detector to detect and analyze at least the source of at least one incoming request; a uniform resource locator (URL) handler to parse said incoming request; a coordinator with access to at least one third party application to coordinate between said URL handler and at least one third party application; a regular renderer to render a regular page comprising content from said website and said at least one third party application; a search engine friendly page renderer to render a search engine friendly page comprising a search engine friendly page of said website and a search engine friendly page of said at least one third party application; a sitemap renderer to render a combined sitemap based on a sitemap of said website and a sitemap of said at least one third party application; and a renderer coordinator to activate one of said regular renderer, said search engine friendly renderer and said sitemap rendered according to said incoming request. ### Claim 2 (depends on 1) The system according to claim 1 and wherein said URL handler comprises: an identifier to identify and extract a page identifier for at least one third party application instance; a redirector to redirect said page identifier to said at least one third party application instance; and a composer to compose an outgoing composite URL using said at least one third party application instance through at least one of URL prefix substitution and callback application programming interface (API) provided to said at least one third party application instance. ### Claim 3 (depends on 2) The system according to claim 2 and wherein said outgoing composite URL provides a deeplink to at least one of said at least of one third party application internal pages and regular website pages on said website and wherein said deeplink is useable from within said third party application. ### Claim 4 (depends on 2) The system according to claim 2 and wherein said at least one third party application instance has at least one of a user and system defined name. ### Claim 5 (depends on 1) The system according to claim 1 and wherein said search engine friendly renderer comprises a substituter to substitute HTML iframe tags and to integrate metadata information from said at least one third party application pages into said search engine friendly page. ### Claim 6 (depends on 1) The system according to claim 1 and wherein entries of said combined sitemap include composite URLs pointing to multiple said at least one third party application pages inside a single containing website page. ### Claim 7 (depends on 1) The system according to claim 1 and wherein said combined sitemap comprises timestamp information provided by said at least one third party application. ### Claim 8 (depends on 1) The system according to claim 1 and wherein said coordinator comprises: a search engine optimization enhancer to enhance search engine optimization for said at least one third party application; and a search engine optimization blocker to block bad search engine optimization techniques for said at least one third party application search engine optimization techniques. ### Claim 9 A method for a website, the method comprising: detecting and analyzing at least the source of at least one incoming request; parsing said incoming request; coordinating between said incoming request and at least one third party application; and rendering a regular website page comprising content from said website and said at least one third party application, rendering a search engine friendly page comprising a search engine friendly page of said website and a search engine friendly page of said at least one third party application; rendering a combined sitemap based on a sitemap of said website and a sitemap of said at least one third party application and; coordinating said rendering a regular website page, rendering a regular website page and rendering a combined sitemap according to said incoming request. ### Claim 10 (depends on 9) The method according to claim 9 and wherein said parsing comprises: identifying and extracting a page identifier for at least one third party application instance; redirecting said page identifier to said at least one third party application instance; and composing an outgoing composite URL using said at least one third party application instance through at least one of URL prefix substitution and callback API provided to said at least one third party application instance. ### Claim 11 (depends on 10) The method according to claim 10 and wherein said outgoing composite URL provides a deeplink to at least one of said at least of one third party application internal pages and regular website pages on said website and wherein said deeplink is useable from within said third party application. ### Claim 12 (depends on 10) The method according to claim 10 and wherein said at least one third party application instance has at least one of a user and system defined name. ### Claim 13 (depends on 9) The method according to claim 9 and wherein said rendering a search engine friendly page comprises substituting hypertext markup language (HTML) iframe tags and integrating metadata information from said at least one third party application pages into said search engine friendly page. ### Claim 14 (depends on 9) The method according to claim 9 and wherein said entries of combined sitemap include composite URLs pointing to multiple said at least one third party application pages inside a single containing website page. ### Claim 15 (depends on 9) The method according to claim 9 and wherein said combined sitemap includes timestamp information provided by said at least one third party application. ### Claim 16 (depends on 9) The system according to claim 9 and wherein said coordinating between comprises: enhancing search engine optimization for said at least one third party application; and blocking bad search engine optimization techniques for said at least one third party application search engine optimization techniques.