Jump to content

Search the Community

Showing results for tags 'seo'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General Discussion
    • Announcements
    • Business Discussion
    • Business Services
    • Sell and Buy
  • Themes & templates
    • KVS default theme
    • KVS paysite theme
  • Educational / support
    • Technical Support
    • FAQ
    • Educational Series

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 7 results

  1. Does changing theme CSS has change son SEO? I made a few changes and site dropped 50% SEO traffic in a coupl eof days.
  2. List of search queries is displayed by search_results block. Here is how you can put it into the main pages: {{insert name="getBlock" block_id="search_results" block_name="Similar Searches"}} Put it into Index and Common Videos List (renders categories, tags, models, content sources and etc.) page templates. After you add this block into page template and save, it will appear in the list of blocks on this page and you can edit its settings. Here is template code for this block that will render cloud of search queries: {{if count($data)>0}} <div class="box search-cloud"> {{foreach item="item" from=$data}} {{assign var="query" value=$item.query|replace:"-":"[dash]"|replace:"&":"%26"|replace:"?":"%3F"|replace:"/":"%2F"|replace:" ":"-"|replace:"[dash]":"--"|rawurlencode}} <a href="{{$lang.urls.search_query|replace:"%QUERY%":$query}}" style="{{if $item.is_bold==1}}font-weight: bold; {{/if}}{{if $item.size>0}}font-size: {{$item.size}}px;{{/if}}">{{$item.query}}</a> &nbsp;&nbsp;&nbsp; {{/foreach}} </div> {{/if}} In block parameters configure: items_per_page: the number of queries you want to be displayed. sort_by: sorting of the queries. var_category_dir = category var_tag_dir = tag size_from = 12 size_to = 16 Also make sure you put a cache time of 86400, as this block will be quite heavy. When this is configured, you can see query cloud is displayed on Index and other video pages. For tag and category pages it should be relevant to the displayed tag / category. On other pages it may render the same set of queries, as they won't have context object that can be used to display similar queries.
  3. Please add the following code to your header template to prepare your video pages for Yandex.Video: {{if $storage.video_view_video_view.video_id>0}} <meta property="og:url" content="{{$storage.video_view_video_view.canonical_url}}"/> <meta property="og:video" content="{{$config.project_url}}/embed/{{$storage.video_view_video_view.video_id}}"/> <meta property="og:type" content="video.other"/> <meta property="og:video:type" content="video/mp4"/> {{if $storage.video_view_video_view.file_dimensions.0>0}} <meta property="og:video:width" content="{{$storage.video_view_video_view.file_dimensions.0}}"/> <meta property="og:video:height" content="{{$storage.video_view_video_view.file_dimensions.1}}"/> {{/if}} {{if $page_og_description==''}} <meta property="og:description" content="{{$storage.video_view_video_view.title|mb_ucfirst}}"/> {{/if}} <meta property="video:duration" content="{{$storage.video_view_video_view.duration_minutes*60+$storage.video_view_video_view.duration_seconds}}"/> {{if $storage.video_view_video_view.tags_as_string}} <meta property="video:tag" content="{{$storage.video_view_video_view.tags_as_string}}"/> {{/if}} <meta property="ya:ovs:upload_date" content="{{$storage.video_view_video_view.post_date|replace:" ":"T"}}"/> <meta property="ya:ovs:adult" content="false"/> <meta property="ya:ovs:allow_embed" content="true"/> <meta property="ya:ovs:views_total" content="{{$storage.video_view_video_view.video_viewed}}"/> <meta property="ya:ovs:comments" content="{{$storage.video_view_video_view.comments_count}}"/> <meta property="ya:ovs:rating" content="{{$storage.video_view_video_view.rating*2}}"/> {{if $storage.video_view_video_view.is_hd==1}} <meta property="ya:ovs:quality" content="HD"/> {{/if}} {{/if}} Also add the following attribute to your <html> tag in header: prefix="og: http://ogp.me/ns# video: http://ogp.me/ns#video"
  4. Hello! How and where to add site description? when i try to find my website on google there is no site description in google search results for my website... can someone tell me where to ad it please?! thank you
  5. KVS doesn't provide any specific GUI controls to manage indexing, as it is not virtually possible due to very custom theme structure. However you can get everything you need with a very few fixes. Step 1. First of all you need to add noindex tag into site header template. Go to Website UI -> Page components -> include_header_general.tpl and add the following code somewhere inside its <head> section: {{if $page_noindex=='true'}} <meta name="robots" content="noindex" /> {{/if}} This code check if there is a page variable named page_noindex and it is equal to true, then this page should not be indexed by SE. Step 2. Set page_noindex variable anywhere you want this page to be not indexable: {{assign var="page_noindex" value="true"}} somewhere in page template around these values (the example is from Index page): How do you find where to add it? If you have KVS 5.3.0 or above, you should be able to see KVS Admin Toolbar at the bottom of each page and you can open page editor right from the toolbar menu. If your KVS version doesn't support toolbar yet, just add ?debug=true to the URL you are looking at and it should open debugger that will print link to open page editor.
  6. General sitemap structure in KVS KVS renders sitemap dynamically as a typical web page configured to produce XML format instead of HTML. You can find sitemap page in Website UI -> Pages -> [system] Sitemap: Due to specific sitemap structure limitations on the number of links, KVS breaks down sitemap into several sitemap indexes, rendering different entities: Videos Albums Playlists Tags Models Categories Sponsors Channels Sitemap indexes that can potentially generate more than 50k links are additionally broken down into paginated sitemaps. That's why sitemap page renders 2 blocks for some object types (videos, albums, playlists, models, tags): one block is for listing all pages (e.g. Sitemaps Videos), another block is for listing all objects per page (e.g. Links to Videos). For categories, sponsors and channels KVS considers that their amount is small, so they are rendered as single lists. Adding search queries into sitemap Since the number of search queries is potentially unlimited, you should consider adding them as 2 blocks similar to models. 1) Open Sitemap page for editing and add the following 2 blocks into it: {{insert name="getBlock" block_id="search_results" block_name="Sitemaps Search Queries"}} {{elseif $smarty.request.type=='search'}} {{insert name="getBlock" block_id="search_results" block_name="Links To Search Queries"}} Here are the highlighted locations where to add these blocks as their position is quite important: 2) Save page editor. After saving you can see that 2 new blocks were added to page structure with default settings: 3) Open Sitemaps Search Queries block for editing. Set its template to the following code: {{section start=1 loop=$nav.page_total+1 name=pages}} <sitemap> <loc>{{$lang.urls.sitemap}}?type=search&amp;from_links_search={{$smarty.section.pages.index}}</loc> <lastmod>{{$smarty.now|date_format:"%Y-%m-%d"}}</lastmod> </sitemap> {{/section}} Set Cache lifetime (s) to 86400. Set the following parameter values: items_per_page = 500 var_from = from_sitemaps_search sort_by = Query text Desc Save this block editor. 4) Open Links To Search Queries block for editing. Set its template to the following code: <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> {{foreach item=item from=$data}} {{assign var="query" value=$item.query|replace:"-":"[dash]"|replace:"&":"%26"|replace:"?":"%3F"|replace:"/":"%2F"|replace:" ":"-"|replace:"[dash]":"--"|rawurlencode}} <url> <loc>{{$lang.urls.search_query|replace:"%QUERY%":$query}}</loc> <lastmod>{{$smarty.now|date_format:"%Y-%m-%d"}}</lastmod> <changefreq>weekly</changefreq> <priority>0.6</priority> </url> {{/foreach}} </urlset> Set Cache lifetime (s) to 86400. Set the following parameter values: items_per_page = 500 var_from = from_links_search sort_by = Query text Desc Save this block editor. 5) Now you should have a fully working search sitemap inside your main sitemap index. Try opening your sitemap and look for "search" keyword: http://domain.com/sitemap.php If your database has search queries, you should see something like this in your sitemap: http://domain.com/sitemap/?type=search&from_links_search=1 http://domain.com/sitemap/?type=search&from_links_search=2 ....
  7. All KVS themes use the same approach of configuring texts and SEO. In admin panel you can change any text in Website UI -> Texts section. You can simply search by the text you want to change and KVS will show you all texts where this fragment is used: SEO In Website UI -> Texts section filter by SEO group. You will see a lot of texts, which can then further be filtered by Page, for example select Index page: For each page you will normally see 3-5 texts like this: html.index_title - for HTML title of this page html.index_description - for HTML description of this page html.index_keywords - for HTML keywords of this page html.index_seo_title - for SEO title displayed on this page html.index_seo_text - for SEO text displayed on this page SEO title and SEO text are not available for every page, normally they are available on Index and on main lists (videos by category, by tag, by model, by search and etc). The other 3 texts are available for all pages. Some pages that render different lists may have many different versions of these texts. For example Common Videos List / Common Albums List pages render videos by category, videos by tag, latest videos, top rated videos and etc. For each of these variants you will see a set of these texts: On Index page you would normally write some static text there, describing your site or whatever you think may be useful for your SEO. When a list page is displayed by category or tag or search, you should normally show different texts for different categories or tags or search requests to have better SEO coverage. You can do that with using tokens, that will be replaced by some data from category, tag and etc. For example search for texts by this external ID: html.videos_by_category. You will see the following 4 texts: These texts are used on page that renders videos list from a specific category. You can see that these texts use some tokens inside them, the tokens will be replaced with some data from category that is currently displayed. So "%title% Videos" will be replaced with "Music Videos" on Music category and "Funny Videos" on Funny category, "%description%" will be replaced with category description and "%synonyms%" will be replaced with category synonyms. You can play with these tokens to get some unique texts for your site. All supported tokens will be listed below. And there is also advanced opportunity to randomize texts for different objects, which is especially useful in tags and search results, where there can be a big variety of different texts. Consider the following example for tag page title: html.videos_by_tag_title = [rand]Free || Cool || Best || HQ || HD || High quality[/rand] %tag% videos There is a [rand]...[/rand] block inside this text. This block will force KVS to take one of the listed fragments randomly for every tag page. So here are different displays for different tags: Free music videos Best funny videos High quality mobile videos ... The key thing here is that random fragment will remain constant for the same tag, unless you update this text notation - updating it will result in another randomization seed. So there will always be "Free" selected for "music" tag and there will always be "Best" selected for "funny" tag. Again, this will remain constant for the time when you don't touch this text anymore. Once you change it (e.g. change the order of words, or anything else in this text), there may be another random fragments selection. You can use [rand]...[/rand] block everywhere in SEO texts (title, desc, keywords, SEO text and title). But title and SEO text / SEO title are the best places for this. Usually it makes sense to use this with tags and search queries due to their big volume. Here are tokens supported for different pages (token meaning should be clear from token name): - Videos / albums by category: %title%, %description%, %synonyms%, %total_videos%, %total_albums%, %total_photos%, %today_videos%, %today_albums%, %custom1% - %custom10%, %first_object_title%, %first_object_description% - Videos / albums by tag: %tag%, %synonyms%, %total_videos%, %total_albums%, %total_photos%, %today_videos%, %today_albums%, %first_object_title%, %first_object_description% - Videos / albums by model: %title%, %description%, %alias%, %country%, %city%, %height%, %weight%, %birth_date%, %age%, %total_videos%, %total_albums%, %total_photos%, %today_videos%, %today_albums%, %custom1% - %custom10%, %first_object_title%, %first_object_description% - Videos / albums by content source: %title%, %description%, %total_videos%, %total_albums%, %total_photos%, %today_videos%, %today_albums%, %categories_as_string%, %group_as_string%, %custom1% - %custom10%, %first_object_title%, %first_object_description% - Videos by channel: %title%, %description%, %total_videos%, %today_videos%, %categories_as_string%, %custom1% - %custom10%, %first_object_title%, %first_object_description% - Videos / albums by search: %search_keyword%, %first_object_title%, %first_object_description% - Video view page: %title%, %description%, %duration%, %rating%, %rating_amount%, %video_viewed%, %username%, %release_year%, %custom1% - %custom3%, %tags_as_string%, %categories_as_string%, %models_as_string%, %content_source_as_string%, %dvd_as_string% - Album view page: %title%, %description%, %photos_amount%, %rating%, %rating_amount%, %album_viewed%, %username%, %custom1% - %custom3%, %tags_as_string%, %categories_as_string%, %models_as_string%, %content_source_as_string% URLs There are 2 places where you can configure URL patterns: In Settings -> Website Settings you can configure system patterns to the main object pages. These patterns are used in admin panel and other system functionality, so they are managed here in this special place: In Website UI -> Texts section you can configure all other URL patterns used by your theme. You can filter them by URL patterns group filter: Some URL patterns also include a token, where dynamic URLs are built (category page, tag page and etc - %DIR% on the above screenshot). If you change such patterns, you should also make sure to keep the same token there, otherwise URL patterns will be broken. Changing URL patterns is not recommended for basic users. In order for new URL patterns to work you will need to add changes to /.htaccess file and modify RewriteRules there. KVS uses mod_rewrite to manage URL mapping, which is difficult to use, but the most flexible way and provides unlimited customization capabilities. Here is small example. If you want for example to change this pattern: urls.albums = /albums/ To: urls.albums = /photos/ you also need to locate the corresponding rule(s) in /.htaccess file. Please be aware that each list page RewriteRule also has a sister rule for pagination, e.g. to make these pages work: /albums/2/ /albums/3/ /albums/4/ ... Usually these 2 sister rules are grouped together: RewriteRule ^albums/([0-9]+)/$ /albums_list.php?from=$1 [L,QSA] RewriteRule ^albums/$ /albums_list.php [L,QSA] You should change pattern in both of them to photos: RewriteRule ^photos/([0-9]+)/$ /albums_list.php?from=$1 [L,QSA] RewriteRule ^photos/$ /albums_list.php [L,QSA] Please note that end of the rule remains the same as before, you only change the first part of rewrite rule (e.g. this part /albums_list.php [L,QSA]). Again, we do not recommend to change this for basic users, URL patterns are not something that much affects anything.
×
×
  • Create New...