4

We use this code in our header embed; allows us to do something like {embed="site/_header" meta_title="Example Title"}; alternatively we can specify an entry ID, and SEO Lite will figure out the correct info, or, we can just let it rely on the last segment, which works 95% of the time. It's worth noting that we're also using Mark Croxton's IfElse add-on ...


2

This is an old topic with plenty of useful information that seems to mirror your question. Hopefully this is helpful to you: https://stackoverflow.com/questions/13213812/getting-the-trailing-slash-back-in-expressionengine-2


2

Pop the following in your header: {exp:seo_lite entry_id="{structure:page:entry_id}"} If you do not add a title into the SEO Lite title field, the entry title will be used for the title meta tag. If you do add a title into the SEO Lite title field, that will be used.


2

For anyone interested the user was helped over here: https://getsatisfaction.com/addonbakery/topics/seo-lite-extra-desc-not-over-riding


2

Below final solution based on category custom fields (thanks to Mark), SEO Lite module, Low Seg2Cat and GWcode Categories plugin in case someone will have similar problem which I had. {if segment_2!="" && segment_3==""} {exp:gwcode_categories show="{segment_2_category_id}" custom_fields="yes" style="linear"} {embed="includes/.header-...


1

To remove postfix in SEO Lite you need to do below changes in SEO Lite >> Settings page. You need to remove {site_name} from Template field and also need to remove  |  from Default title postfix field in Settings page of SEO Lite module. So, above steps will remove Default Postfix. Also see screenshot for more reference. After making above ...


1

Try changing the line $this->EE->cp->set_variable('cp_page_title', lang($lang_key)); to $this->EE->view->cp_page_title = lang($lang_key);


1

Yepp, the homepage is a special case as it does not have an url_title which you need if you use the "use_last_segment" parameter. So you'll have to fetch it using entry_id, or alternatively modify the default SEO Lite template in the CP to fit the homepage.


1

I got it figured out. In my main layout I used the following, where the entry ID of 11 is the ID for the home page entry: {if segment_1 ==""} {exp:seo_lite entry_id="11"} {if:else} {exp:seo_lite use_last_segment='yes'} {/if}


1

The only thing I can think of in your case is to specify some default in the description or keywords that you know and can check against. So, if SEO Lite defaults you'll know about it and can then use the ones from the entry. The way I usually do this though is with extra tags, have you looked at those? http://wedoaddons.com/seo-lite/extra-tags


1

Why not just create additional Category Custom Fields? They are quite limiting but a Text Input for Keywords and a Text Area field should suffice for meta data. You can read more about them here: https://ellislab.com/expressionengine/user-guide/cp/admin/channels/category_field_management.html


1

I found that I wanted my meta description to be populated with the following priority: Custom SEO Description in entry edit SEO Lite tab Extracted {extra:desc} value from my entry Fallback site-wide Default description set in SEO Lite settings I couldn't find a way to do this with SEO Lite as it stands, so I decide to add a new variables that I could use ...


1

there is an easier way to do this with SEO Lite, check out this gist which has an example: https://gist.github.com/bjornbjorn/4039233


1

In general, don't try to force EE to use a trailing slash. Do the opposite - make the canonical links without a trailing slash. Seriously, that is the way EE likes it, and you are pushing shit uphill trying to do anything else. Don't use a 301 htaccess redirect - that's ridiculous, because EE generates all URLs without a trailing slash. Then you would be ...


1

Have you seen my blog post on SEO & ExpressionEngine. I'm sure using that approach would get you partway to what you want to do. Additionally I would take a look at SurgEEo - which I believe addresses some of what I was trying to do in the blog post linked above. I'm going to be trying out SurgEEo on my next build so can't guarantee this yet.


Only top voted, non community-wiki answers of a minimum length are eligible